| commit | 70456600f42f85cfcbdd9d7a6029c03b6f9c5d1e | |
| author | Michael Halcrow <mhalcrow@us.ibm.com> | |
| Mon, 12 Feb 2007 08:53:48 +0000 (12 00:53 -0800) | ||
| committer | Linus Torvalds <torvalds@woody.linux-foundation.org> | |
| Mon, 12 Feb 2007 17:48:37 +0000 (12 09:48 -0800) | ||
| tree | 1b47957d59bfe3b4e5e5244106678f5542f8f295 | treesnapshot (tar.gz zip) |
| parent | e77a56ddceeec87575a13a60fc1a394af6a1f4bc | commitdiff |
[PATCH] eCryptfs: convert f_op->write() to vfs_write()
sys_write() takes a local copy of f_pos and writes that back
into the struct file. It does this so that two concurrent write()
callers don't make a mess of f_pos, and of the file contents.
ecryptfs should be calling vfs_write(). That way we also get the fsnotify
notifications, which ecryptfs presently appears to have subverted.
Convert direct calls to f_op->write() into calls to vfs_write().
Signed-off-by: Michael Halcrow <mhalcrow@us.ibm.com>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
sys_write() takes a local copy of f_pos and writes that back
into the struct file. It does this so that two concurrent write()
callers don't make a mess of f_pos, and of the file contents.
ecryptfs should be calling vfs_write(). That way we also get the fsnotify
notifications, which ecryptfs presently appears to have subverted.
Convert direct calls to f_op->write() into calls to vfs_write().
Signed-off-by: Michael Halcrow <mhalcrow@us.ibm.com>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
| fs/ecryptfs/crypto.c | diffblobblamehistory | |
| fs/ecryptfs/inode.c | diffblobblamehistory |