[PATCH] PATCH 3/7: knfsd cleanups - incorrect use of inode_change_ok
authorNeil Brown <neilb@cse.unsw.edu.au>
Mon, 18 Feb 2002 00:40:02 +0000 (16:40 -0800)
committerLinus Torvalds <torvalds@home.transmeta.com>
Mon, 18 Feb 2002 00:40:02 +0000 (16:40 -0800)
commitc5d135532e043df0d7291bc937db3888997727b4
tree4f4d67ce42e490cf5339d33c6b7cb1df986f35ef
parent93c936585479bd7b23d2f41d97d9aa39fcef6184
[PATCH] PATCH 3/7: knfsd cleanups - incorrect use of inode_change_ok

Get nfsd_setattr to not put too much weight on inode_change_ok

nfsd_currently calls inode_change_ok and does not try setattr if this fails.
However this is wrong.  If a filesystem defines it's own i_op->setattr, then
it might use a completely different mechanisim for determining what is ok.
nfsd shouldn't assume...

We still use inode_change_ok when normalising NFSv2 "touch" requests, but
only in passing.
fs/nfsd/vfs.c