Brian Behlendorf 3117dd0b90 Handle NULL in nfsd .fsync() hook ... How nfsd handles .fsync() has been changed a couple of times in the recent kernels. But basically there are three cases we need to consider. Linux 2.6.12 - 2.6.33 * The .fsync() hook takes 3 arguments * The nfsd will call .fsync() with a NULL file struct pointer. Linux 2.6.34 * The .fsync() hook takes 3 arguments * The nfsd no longer calls .fsync() but instead used sync_inode() Linux 2.6.35 - 2.6.x * The .fsync() hook takes 2 arguments * The nfsd no longer calls .fsync() but instead used sync_inode() For once it looks like we've gotten lucky. The first two cases can actually be collased in to one if we stop using the file struct pointer entirely. Since the dentry is still passed in both cases this is possible. The last case can then be safely handled by unconditionally using the dentry in the file struct pointer now that we know the nfsd caller has been removed. Closes #230		2011-05-06 12:33:45 -07:00
..
blkdev_compat.h	Linux 2.6.27 compat, blk_queue_stackable()	2011-03-22 12:15:54 -07:00
dcache_compat.h	Add Linux Compat Infrastructure	2011-02-10 09:25:10 -08:00
Makefile.am	Add the new blkdev_compat.h header to the DIST target.	2011-02-24 09:40:06 -08:00
Makefile.in	Fix 'zfs set volsize=N pool/dataset'	2011-05-02 08:54:40 -07:00
vfs_compat.h	Handle NULL in nfsd .fsync() hook	2011-05-06 12:33:45 -07:00
xattr_compat.h	Linux 2.6.33 compat, get/set xattr callbacks	2011-02-11 10:41:00 -08:00