summaryrefslogtreecommitdiff
path: root/fs/omfs
diff options
context:
space:
mode:
authorJeff Layton <jlayton@redhat.com>2010-12-07 21:19:50 (GMT)
committerAl Viro <viro@zeniv.linux.org.uk>2011-01-13 01:06:59 (GMT)
commite1181ee6575d7970bad15aaa852784b4972d2af8 (patch)
treecf1010ee6361e8bcd98ea2f29fa899fa52bf801d /fs/omfs
parentcccb5a1e698535fa5a734ffe21c7061c97f8d8c5 (diff)
downloadlinux-fsl-qoriq-e1181ee6575d7970bad15aaa852784b4972d2af8.tar.xz
vfs: pass struct file to do_truncate on O_TRUNC opens (try #2)
When a file is opened with O_TRUNC, the truncate processing is handled by handle_truncate(). This function however doesn't receive any info about the newly instantiated filp, and therefore can't pass that info along so that the setattr can use it. This makes NFSv4 misbehave. The client does an open and gets a valid stateid, and then doesn't use that stateid on the subsequent truncate. It uses the zero-stateid instead. Most servers ignore this fact and just do the truncate anyway, but some don't like it (notably, RHEL4). It seems more correct that since we have a fully instantiated file at the time that handle_truncate is called, that we pass that along so that the truncate operation can properly use it. Signed-off-by: Jeff Layton <jlayton@redhat.com> Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>
Diffstat (limited to 'fs/omfs')
0 files changed, 0 insertions, 0 deletions