linux.git/fs/logfs/segment.c, branch v4.5

logfs: constify logfs_block_ops structures

2016-01-09T07:55:45+00:00

The logfs_block_ops structures are never modified, so declare them as
const.

Done with the help of Coccinelle.

Signed-off-by: Julia Lawall 
Signed-off-by: Al Viro

mm, fs: introduce mapping_gfp_constraint()

2015-11-07T01:50:42+00:00

There are many places which use mapping_gfp_mask to restrict a more
generic gfp mask which would be used for allocations which are not
directly related to the page cache but they are performed in the same
context.

Let's introduce a helper function which makes the restriction explicit and
easier to track.  This patch doesn't introduce any functional changes.

[akpm@linux-foundation.org: coding-style fixes]
Signed-off-by: Michal Hocko 
Suggested-by: Andrew Morton 
Signed-off-by: Andrew Morton 
Signed-off-by: Linus Torvalds

logfs: check for the return value after calling find_or_create_page()

2014-01-24T00:36:54+00:00

In get_mapping_page(), after calling find_or_create_page(), the return
value should be checked.

 This patch has been provided:
http://www.spinics.net/lists/linux-fsdevel/msg66948.html but not been
applied now.

Signed-off-by: Younger Liu 
Cc: Younger Liu 
Cc: Vyacheslav Dubeyko 
Reviewed-by: Prasad Joshi 
Cc: Jörn Engel 
Signed-off-by: Andrew Morton 
Signed-off-by: Linus Torvalds

mm: change invalidatepage prototype to accept length

2013-05-22T03:17:23+00:00

Currently there is no way to truncate partial page where the end
truncate point is not at the end of the page. This is because it was not
needed and the functionality was enough for file system truncate
operation to work properly. However more file systems now support punch
hole feature and it can benefit from mm supporting truncating page just
up to the certain point.

Specifically, with this functionality truncate_inode_pages_range() can
be changed so it supports truncating partial page at the end of the
range (currently it will BUG_ON() if 'end' is not at the end of the
page).

This commit changes the invalidatepage() address space operation
prototype to accept range to be invalidated and update all the instances
for it.

We also change the block_invalidatepage() in the same way and actually
make a use of the new length argument implementing range invalidation.

Actual file system implementations will follow except the file systems
where the changes are really simple and should not change the behaviour
in any way .Implementation for truncate_page_range() which will be able
to accept page unaligned ranges will follow as well.

Signed-off-by: Lukas Czerner 
Cc: Andrew Morton 
Cc: Hugh Dickins

logfs: destroy the reserved inodes while unmounting

2012-04-02T03:50:33+00:00

We were assuming that the evict_inode() would never be called on
reserved inodes. However, (after the commit 8e22c1a4e logfs: get rid
of magical inodes) while unmounting the file system, in put_super, we
call iput() on all of the reserved inodes.

The following simple test used to cause a kernel panic on LogFS:

1. Mount a LogFS file system on /mnt

2. Create a file
   $ touch /mnt/a

3. Try to unmount the FS
   $ umount /mnt

The simple fix would be to drop the assumption and properly destroy
the reserved inodes.

Signed-off-by: Prasad Joshi

logfs: remove the second argument of k[un]map_atomic()

2012-03-20T13:48:24+00:00

Signed-off-by: Cong Wang

logfs: Free areas before calling generic_shutdown_super()

2012-01-28T06:12:39+00:00

Or hit an assertion in map_invalidatepage() instead.

Signed-off-by: Joern Engel

logfs: update page reference count for pined pages

2012-01-28T05:53:10+00:00

LogFS sets PG_private flag to indicate a pined page. We assumed that
marking a page as private is enough to ensure its existence. But
instead it is necessary to hold a reference count to the page.

The change resolves the following BUG

BUG: Bad page state in process flush-253:16  pfn:6a6d0
page flags: 0x100000000000808(uptodate|private)

Suggested-and-Acked-by: Joern Engel 
Signed-off-by: Prasad Joshi

logfs: get rid of magical inodes

2010-08-09T20:48:26+00:00

ordering problems at ->kill_sb() time are solved by doing iput()
of these suckers in ->put_super()

Signed-off-by: Al Viro

logfs: survive logfs_buf_recover read errors

2010-05-04T17:37:04+00:00

Refusing to mount beats a kernel crash.

Signed-off-by: Joern Engel