]> git.karo-electronics.de Git - karo-tx-linux.git/commit
nfsd: Fix possible BUG_ON firing in set_change_info
authorNeil Brown <neilb@suse.de>
Thu, 2 Dec 2010 00:14:30 +0000 (11:14 +1100)
committerGreg Kroah-Hartman <gregkh@suse.de>
Fri, 7 Jan 2011 21:58:16 +0000 (13:58 -0800)
commit972dc03c6d6ab89c45fbcf4e286a35e124cadcd4
tree4e2b36cc37b1bad7476e31d38fb8104ce6f16312
parent1e4d3ed637822285360fdefb42608feb1bdfefa7
nfsd: Fix possible BUG_ON firing in set_change_info

commit c1ac3ffcd0bc7e9617f62be8c7043d53ab84deac upstream.

If vfs_getattr in fill_post_wcc returns an error, we don't
set fh_post_change.
For NFSv4, this can result in set_change_info triggering a BUG_ON.
i.e. fh_post_saved being zero isn't really a bug.

So:
 - instead of BUGging when fh_post_saved is zero, just clear ->atomic.
 - if vfs_getattr fails in fill_post_wcc, take a copy of i_ctime anyway.
   This will be used i seg_change_info, but not overly trusted.
 - While we are there, remove the pointless 'if' statements in set_change_info.
   There is no harm setting all the values.

Signed-off-by: NeilBrown <neilb@suse.de>
Signed-off-by: J. Bruce Fields <bfields@redhat.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
fs/nfsd/nfs3xdr.c
fs/nfsd/xdr4.h