LOLi ae5b4a05ff 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 16:46:54 -07:00
..
.gitignore	Add .gitignore files to exclude build products	2010-01-08 11:35:17 -08:00
Makefile.am	GCC 7.1 fixes	2017-06-28 10:05:16 -07:00
ztest.c	Fix range locking in ZIL commit codepath	2017-08-21 16:46:54 -07:00