summaryrefslogtreecommitdiffstats
path: root/fs/ext3
diff options
context:
space:
mode:
authorEric Sandeen <sandeen@redhat.com>2012-04-30 13:11:29 -0500
committerAl Viro <viro@zeniv.linux.org.uk>2012-07-23 00:00:15 +0400
commite8b96eb5034a0ccebf36760f88e31ea3e3cdf1e4 (patch)
tree3ea1b85311b3d059f2bbf38e484aa2ce06bab017 /fs/ext3
parent4ea425b63a3dfeb7707fc7cc7161c11a51e871ed (diff)
downloadop-kernel-dev-e8b96eb5034a0ccebf36760f88e31ea3e3cdf1e4.zip
op-kernel-dev-e8b96eb5034a0ccebf36760f88e31ea3e3cdf1e4.tar.gz
vfs: allow custom EOF in generic_file_llseek code
For ext3/4 htree directories, using the vfs llseek function with SEEK_END goes to i_size like for any other file, but in reality we want the maximum possible hash value. Recent changes in ext4 have cut & pasted generic_file_llseek() back into fs/ext4/dir.c, but replicating this core code seems like a bad idea, especially since the copy has already diverged from the vfs. This patch updates generic_file_llseek_size to accept both a custom maximum offset, and a custom EOF position. With this in place, ext4_dir_llseek can pass in the appropriate maximum hash position for both maxsize and eof, and get what it wants. As far as I know, this does not fix any bugs - nfs in the kernel doesn't use SEEK_END, and I don't know of any user who does. But some ext4 folks seem keen on doing the right thing here, and I can't really argue. (Patch also fixes up some comments slightly) Signed-off-by: Eric Sandeen <sandeen@redhat.com> Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>
Diffstat (limited to 'fs/ext3')
-rw-r--r--fs/ext3/dir.c3
1 files changed, 2 insertions, 1 deletions
diff --git a/fs/ext3/dir.c b/fs/ext3/dir.c
index 92490e9..901f67e 100644
--- a/fs/ext3/dir.c
+++ b/fs/ext3/dir.c
@@ -303,7 +303,8 @@ loff_t ext3_dir_llseek(struct file *file, loff_t offset, int origin)
if (likely(dx_dir))
return generic_file_llseek_size(file, offset, origin,
- ext3_get_htree_eof(file));
+ ext3_get_htree_eof(file),
+ i_size_read(inode));
else
return generic_file_llseek(file, offset, origin);
}
OpenPOWER on IntegriCloud