LOLi f763c3d1df Fix range locking in ZIL commit codepath ... Since OpenZFS 7578 (1b7c1e5) if we have a ZVOL with logbias=throughput we will force WR_INDIRECT itxs in zvol_log_write() setting itx->itx_lr offset and length to the offset and length of the BIO from zvol_write()->zvol_log_write(): these offset and length are later used to take a range lock in zillog->zl_get_data function: zvol_get_data(). Now suppose we have a ZVOL with blocksize=8K and push 4K writes to offset 0: we will only be range-locking 0-4096. This means the ASSERTion we make in dbuf_unoverride() is no longer valid because now dmu_sync() is called from zilog's get_data functions holding a partial lock on the dbuf. Fix this by taking a range lock on the whole block in zvol_get_data(). Reviewed-by: Chunwei Chen <tuxoko@gmail.com> Reviewed-by: Brian Behlendorf <behlendorf1@llnl.gov> Signed-off-by: loli10K <ezomori.nozomu@gmail.com> Closes #6238 Closes #6315 Closes #6356 Closes #6477		2017-08-21 08:59:48 -07:00
..
avl	Fix uninitialized variable in avl_add()	2016-07-25 14:21:34 -07:00
icp	Retire legacy test infrastructure	2017-08-15 17:26:38 -07:00
nvpair	OpenZFS 7812 - Remove gender specific language	2017-02-24 11:07:04 -08:00
unicode	codebase style improvements for OpenZFS 6459 port	2017-01-22 13:25:40 -08:00
zcommon	Native Encryption for ZFS on Linux	2017-08-14 10:36:48 -07:00
zfs	Fix range locking in ZIL commit codepath	2017-08-21 08:59:48 -07:00
.gitignore	Improve gitignore	2017-05-25 10:14:13 -07:00
Makefile.in	Retire legacy test infrastructure	2017-08-15 17:26:38 -07:00