Brian Behlendorf 2a53e2dacc Update inode under range lock ... After a successful write the inode must be updated under the range lock. If it is updated after dropping the lock there exists a race where the znode and inode wile disagree about the file size. This could result in narrow window of time where read(2) is able to access data beyond what fstat(2) reports as the file size. Signed-off-by: Brian Behlendorf <behlendorf1@llnl.gov> Signed-off-by: Ned Bass <bass6@llnl.gov> Closes #3601		2015-07-17 09:18:22 -07:00
..
avl	Illumos 4745 - fix AVL code misspellings	2015-07-10 11:58:37 -07:00
nvpair	Retire spl_module_init()/spl_module_fini()	2015-02-24 11:37:44 -08:00
unicode	Retire spl_module_init()/spl_module_fini()	2015-02-24 11:37:44 -08:00
zcommon	Illumos 5027 - zfs large block support	2015-05-11 12:23:16 -07:00
zfs	Update inode under range lock	2015-07-17 09:18:22 -07:00
zpios	Retire spl_module_init()/spl_module_fini()	2015-02-24 11:37:44 -08:00
.gitignore	gitignore: anchor entries at their respective directory	2013-04-02 10:50:17 -07:00
Makefile.in	Fix modules installation directory	2014-10-28 09:46:14 -07:00