Neil Brown 54cc1ed394 nfsd: Fix possible BUG_ON firing in set_change_info ... commit c1ac3ffcd0 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>		2011-01-07 14:43:04 -08:00
..
cache.h	knfsd: reply cache cleanups	2009-05-27 14:14:02 -04:00
const.h
debug.h
export.h	switch rqst_exp_parent()	2009-06-11 21:36:00 -04:00
Kbuild
nfsd.h	seq_file: constify seq_operations	2009-09-23 07:39:29 -07:00
nfsfh.h	nfsd: support ext4 i_version	2009-04-29 11:35:49 -04:00
state.h	nfsd41: Backchannel: Setup sequence information	2009-09-15 20:49:56 -04:00
stats.h	Fix a build warning about leaking CONFIG_NFSD to userspace.	2009-03-27 19:48:36 -04:00
syscall.h	headers_check fix: nfsd/syscall.h	2009-01-30 23:30:42 +05:30
xdr.h
xdr3.h
xdr4.h	nfsd: Fix possible BUG_ON firing in set_change_info	2011-01-07 14:43:04 -08:00