[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <20240731-debug-v3-0-f9b7ed479b10@kernel.org>
Date: Wed, 31 Jul 2024 22:43:02 +0200
From: Johannes Thumshirn <jth@...nel.org>
To: Chris Mason <clm@...com>, Josef Bacik <josef@...icpanda.com>,
David Sterba <dsterba@...e.com>
Cc: linux-btrfs@...r.kernel.org, linux-kernel@...r.kernel.org,
Johannes Thumshirn <johannes.thumshirn@....com>, Qu Wenruo <wqu@...e.com>,
Johannes Thumshirn <jthumshirn@....com>, Filipe Manana <fdmanana@...e.com>
Subject: [PATCH v3 0/5] btrfs: fix relocation on RAID stripe-tree
filesystems
When doing relocation on RST backed filesystems, there is a possibility of
a scatter-gather list corruption.
See patch 4 for details.
CI Link: https://github.com/btrfs/linux/actions/runs/10143804038
---
Changes in v3:
- Re-base onto for-next with folio->page conversion applied.
- Collected reviews.
- Link to v2: https://lore.kernel.org/r/20240730-debug-v2-0-38e6607ecba6@kernel.org
Changes in v2:
- Change RST lookup error message to debug
- Link to v1: https://lore.kernel.org/r/20240729-debug-v1-0-f0b3d78d9438@kernel.org
---
Johannes Thumshirn (5):
btrfs: don't dump stripe-tree on lookup error
btrfs: rename btrfs_io_stripe::is_scrub to rst_search_commit_root
btrfs: set rst_search_commit_root in case of relocation
btrfs: don't readahead the relocation inode on RST
btrfs: change RST lookup error message to debug
fs/btrfs/bio.c | 3 ++-
fs/btrfs/raid-stripe-tree.c | 8 +++-----
fs/btrfs/relocation.c | 14 ++++++++++----
fs/btrfs/scrub.c | 2 +-
fs/btrfs/volumes.h | 2 +-
5 files changed, 17 insertions(+), 12 deletions(-)
---
base-commit: 27d58e7d992b58ae7091270dc179e1dcbd6561f8
change-id: 20240726-debug-f1fe805ea37b
Best regards,
--
Johannes Thumshirn <jth@...nel.org>
Powered by blists - more mailing lists