diff options
author | Christoph Hellwig <hch@lst.de> | 2023-05-15 12:18:21 +0300 |
---|---|---|
committer | David Sterba <dsterba@suse.com> | 2023-05-27 00:24:01 +0300 |
commit | 45c2f36871955b51b4ce083c447388d8c72d6b91 (patch) | |
tree | fe3f782d3e0305c8fd21f7ef37c81786f8d1926a /fs/fuse | |
parent | 597441b3436a43011f31ce71dc0a6c0bf5ce958a (diff) | |
download | linux-45c2f36871955b51b4ce083c447388d8c72d6b91.tar.xz |
btrfs: call btrfs_orig_bbio_end_io in btrfs_end_bio_work
When I implemented the storage layer bio splitting, I was under the
assumption that we'll never split metadata bios. But Qu reminded me that
this can actually happen with very old file systems with unaligned
metadata chunks and RAID0.
I still haven't seen such a case in practice, but we better handled this
case, especially as it is fairly easily to do not calling the ->end_іo
method directly in btrfs_end_io_work, and using the proper
btrfs_orig_bbio_end_io helper instead.
In addition to the old file system with unaligned metadata chunks case
documented in the commit log, the combination of the new scrub code
with Johannes pending raid-stripe-tree also triggers this case. We
spent some time debugging it and found that this patch solves
the problem.
Fixes: 103c19723c80 ("btrfs: split the bio submission path into a separate file")
CC: stable@vger.kernel.org # 6.3+
Reviewed-by: Johannes Thumshirn <johannes.thumshirn@wdc.com>
Tested-by: Johannes Thumshirn <johannes.thumshirn@wdc.com>
Signed-off-by: Christoph Hellwig <hch@lst.de>
Signed-off-by: David Sterba <dsterba@suse.com>
Diffstat (limited to 'fs/fuse')
0 files changed, 0 insertions, 0 deletions