[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.
Showing
Please register or sign in to comment