diff options
| author | Naohiro Aota <naohiro.aota@wdc.com> | 2025-12-17 20:14:04 +0900 |
|---|---|---|
| committer | Sasha Levin <sashal@kernel.org> | 2026-03-04 07:21:21 -0500 |
| commit | 72f6529487a378d24d664167076d85d8f30c12d1 (patch) | |
| tree | 2f07802930873db67cd461ecbc1611a026670033 /tools/perf/scripts/python/stackcollapse.py | |
| parent | 25afd2a1ee4d2d5470dc0945ff412e2625eb867a (diff) | |
| download | kernel-72f6529487a378d24d664167076d85d8f30c12d1.tar.gz | |
btrfs: zoned: fixup last alloc pointer after extent removal for RAID1
[ Upstream commit dda3ec9ee6b3e120603bff1b798f25b51e54ac5d ]
When a block group is composed of a sequential write zone and a
conventional zone, we recover the (pseudo) write pointer of the
conventional zone using the end of the last allocated position.
However, if the last extent in a block group is removed, the last extent
position will be smaller than the other real write pointer position.
Then, that will cause an error due to mismatch of the write pointers.
We can fixup this case by moving the alloc_offset to the corresponding
write pointer position.
Fixes: 568220fa9657 ("btrfs: zoned: support RAID0/1/10 on top of raid stripe tree")
CC: stable@vger.kernel.org # 6.12+
Reviewed-by: Johannes Thumshirn <johannes.thumshirn@wdc.com>
Signed-off-by: Naohiro Aota <naohiro.aota@wdc.com>
Signed-off-by: David Sterba <dsterba@suse.com>
Signed-off-by: Sasha Levin <sashal@kernel.org>
Diffstat (limited to 'tools/perf/scripts/python/stackcollapse.py')
0 files changed, 0 insertions, 0 deletions
