mirror of
https://github.com/hardkernel/linux.git
synced 2026-03-26 04:20:23 +09:00
btrfs: zero the buffer before marking it dirty in btrfs_redirty_list_add
commitc83b56d1ddupstream. btrfs_redirty_list_add zeroes the buffer data and sets the EXTENT_BUFFER_NO_CHECK to make sure writeback is fine with a bogus header. But it does that after already marking the buffer dirty, which means that writeback could already be looking at the buffer. Switch the order of operations around so that the buffer is only marked dirty when we're ready to write it. Fixes:d3575156f6("btrfs: zoned: redirty released extent buffers") CC: stable@vger.kernel.org # 5.15+ Signed-off-by: Christoph Hellwig <hch@lst.de> Reviewed-by: David Sterba <dsterba@suse.com> Signed-off-by: David Sterba <dsterba@suse.com> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
This commit is contained in:
committed by
Greg Kroah-Hartman
parent
f264be2414
commit
bcc401bb86
@@ -1347,11 +1347,11 @@ void btrfs_redirty_list_add(struct btrfs_transaction *trans,
|
||||
!list_empty(&eb->release_list))
|
||||
return;
|
||||
|
||||
memzero_extent_buffer(eb, 0, eb->len);
|
||||
set_bit(EXTENT_BUFFER_NO_CHECK, &eb->bflags);
|
||||
set_extent_buffer_dirty(eb);
|
||||
set_extent_bits_nowait(&trans->dirty_pages, eb->start,
|
||||
eb->start + eb->len - 1, EXTENT_DIRTY);
|
||||
memzero_extent_buffer(eb, 0, eb->len);
|
||||
set_bit(EXTENT_BUFFER_NO_CHECK, &eb->bflags);
|
||||
|
||||
spin_lock(&trans->releasing_ebs_lock);
|
||||
list_add_tail(&eb->release_list, &trans->releasing_ebs);
|
||||
|
||||
Reference in New Issue
Block a user