diff options
author | Matthew Ahrens <[email protected]> | 2017-04-14 12:59:18 -0700 |
---|---|---|
committer | Brian Behlendorf <[email protected]> | 2017-07-04 15:41:24 -0700 |
commit | 02dc43bc4615537e8e198170a0711e317c8e6dda (patch) | |
tree | 4867dbc985b020863ef8a53df03b86d3ecb89901 /module/zfs/zio_checksum.c | |
parent | 8ca78ab00278332a877d7d95e057c0b4aca5f9ad (diff) |
OpenZFS 8378 - crash due to bp in-memory modification of nopwrite block
Authored by: Matthew Ahrens <[email protected]>
Reviewed by: Prakash Surya <[email protected]>
Reviewed by: George Wilson <[email protected]>
Approved by: Robert Mustacchi <[email protected]>
Reviewed-by: Brian Behlendorf <[email protected]>
Ported-by: Giuseppe Di Natale <[email protected]>
The problem is that zfs_get_data() supplies a stale zgd_bp to
dmu_sync(), which we then nopwrite against.
zfs_get_data() doesn't hold any DMU-related locks, so after it
copies db_blkptr to zgd_bp, dbuf_write_ready() could change
db_blkptr, and dbuf_write_done() could remove the dirty record.
dmu_sync() then sees the stale BP and that the dbuf it not dirty,
so it is eligible for nop-writing.
The fix is for dmu_sync() to copy db_blkptr to zgd_bp after
acquiring the db_mtx. We could still see a stale db_blkptr,
but if it is stale then the dirty record will still exist and
thus we won't attempt to nopwrite.
OpenZFS-issue: https://www.illumos.org/issues/8378
OpenZFS-commit: https://github.com/openzfs/openzfs/commit/3127742
Closes #6293
Diffstat (limited to 'module/zfs/zio_checksum.c')
0 files changed, 0 insertions, 0 deletions