linux-toradex.git/fs/logfs/file.c, branch v4.5

wrappers for ->i_mutex access

2016-01-22T23:04:28+00:00

parallel to mutex_{lock,unlock,trylock,is_locked,lock_nested},
inode_foo(inode) being mutex_foo(&inode->i_mutex).

Please, use those for access to ->i_mutex; over the coming cycle
->i_mutex will become rwsem, with ->lookup() done with it held
only shared.

Signed-off-by: Al Viro

VFS: normal filesystems (and lustre): d_inode() annotations

2015-04-15T19:06:57+00:00

that's the bulk of filesystem drivers dealing with inodes of their own

Signed-off-by: David Howells 
Signed-off-by: Al Viro

make new_sync_{read,write}() static

2015-04-12T02:29:40+00:00

All places outside of core VFS that checked ->read and ->write for being NULL or
called the methods directly are gone now, so NULL {read,write} with non-NULL
{read,write}_iter will do the right thing in all cases.

Signed-off-by: Al Viro

write_iter variants of {__,}generic_file_aio_write()

2014-05-06T21:38:00+00:00

Signed-off-by: Al Viro

switch simple generic_file_aio_read() users to ->read_iter()

2014-05-06T21:37:55+00:00

Signed-off-by: Al Viro

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

new helper: file_inode(file)

2013-02-23T04:31:31+00:00

Signed-off-by: Al Viro

logfs: take write mutex lock during fsync and sync

2012-01-28T06:06:06+00:00

LogFS uses super->s_write_mutex while writing data to disk. Taking the
same mutex lock in sync and fsync code path solves the following BUG:

------------[ cut here ]------------
kernel BUG at /home/prasad/logfs/dev_bdev.c:134!

Pid: 2387, comm: flush-253:16 Not tainted 3.0.0+ #4 Bochs Bochs
RIP: 0010:[]  []
                bdev_writeseg+0x25d/0x270 [logfs]
Call Trace:
[] logfs_open_area+0x91/0x150 [logfs]
[] ? find_level.clone.9+0x62/0x100
[] __logfs_segment_write.clone.20+0x5c/0x190 [logfs]
[] ? mempool_kmalloc+0x15/0x20
[] ? mempool_alloc+0x53/0x130
[] logfs_segment_write+0x1d4/0x230 [logfs]
[] logfs_write_i0+0x12e/0x190 [logfs]
[] __logfs_write_rec+0x140/0x220 [logfs]
[] logfs_write_rec+0x64/0xd0 [logfs]
[] __logfs_write_buf+0x106/0x110 [logfs]
[] logfs_write_buf+0x4e/0x80 [logfs]
[] __logfs_writepage+0x23/0x80 [logfs]
[] logfs_writepage+0xdc/0x110 [logfs]
[] __writepage+0x17/0x40
[] write_cache_pages+0x208/0x4f0
[] ? set_page_dirty+0x70/0x70
[] generic_writepages+0x4a/0x70
[] do_writepages+0x21/0x40
[] writeback_single_inode+0x101/0x250
[] writeback_sb_inodes+0xed/0x1c0
[] writeback_inodes_wb+0x7b/0x1e0
[] wb_writeback+0x4c3/0x530
[] ? sub_preempt_count+0x9d/0xd0
[] wb_do_writeback+0xdb/0x290
[] ? sub_preempt_count+0x9d/0xd0
[] ? _raw_spin_unlock_irqrestore+0x18/0x40
[] ? del_timer+0x8a/0x120
[] bdi_writeback_thread+0x8c/0x2e0
[] ? wb_do_writeback+0x290/0x290
[] kthread+0x96/0xa0
[] kernel_thread_helper+0x4/0x10
[] ? kthread_worker_fn+0x190/0x190
[] ? gs_change+0xb/0xb
RIP  [] bdev_writeseg+0x25d/0x270 [logfs]
---[ end trace 0211ad60a57657c4 ]---

Reviewed-by: Joern Engel 
Signed-off-by: Prasad Joshi

fs: push i_mutex and filemap_write_and_wait down into ->fsync() handlers

2011-07-21T00:47:59+00:00

Btrfs needs to be able to control how filemap_write_and_wait_range() is called
in fsync to make it less of a painful operation, so push down taking i_mutex and
the calling of filemap_write_and_wait() down into the ->fsync() handlers.  Some
file systems can drop taking the i_mutex altogether it seems, like ext3 and
ocfs2.  For correctness sake I just pushed everything down in all cases to make
sure that we keep the current behavior the same for everybody, and then each
individual fs maintainer can make up their mind about what to do from there.
Thanks,

Acked-by: Jan Kara 
Signed-off-by: Josef Bacik 
Signed-off-by: Al Viro

userns: rename is_owner_or_cap to inode_owner_or_capable

2011-03-24T02:47:13+00:00

And give it a kernel-doc comment.

[akpm@linux-foundation.org: btrfs changed in linux-next]
Signed-off-by: Serge E. Hallyn 
Cc: "Eric W. Biederman" 
Cc: Daniel Lezcano 
Acked-by: David Howells 
Cc: James Morris 
Signed-off-by: Andrew Morton 
Signed-off-by: Linus Torvalds