diff options
| author | Darrick J. Wong <djwong@kernel.org> | 2026-10-12 23:06:30 -0700 |
|---|---|---|
| committer | Carlos Maiolino <cem@kernel.org> | 2026-10-14 09:49:28 +0200 |
| commit | 219ff8a734d8438e24eb346a847c9b1ad9b7ab5d (patch) | |
| tree | 42880c3f98d3bb9e0bbdccbe0f15b8040cf563e8 /tools/perf/scripts/python/bin/stackcollapse-record | |
| parent | 80f13dc7225eec318da7499c7a562d7a34d25e6a (diff) | |
| download | linux-219ff8a734d8438e24eb346a847c9b1ad9b7ab5d.tar.gz linux-219ff8a734d8438e24eb346a847c9b1ad9b7ab5d.zip | |
xfs: don't queue rmap update twice when reaping a fork
LOLLM noticed that xrep_reap_bmapi_iter calls xfs_bmap_unmap_extent and
xfs_rmap_unmap_extent to remove a mapping from a file fork and its
reverse mapping. However, xfs_bmap_del_extent_real also queues a
deferred rmap removal log item, which means that we incorrectly queue
two rmap removal operations. Fix that by removing the extra call and
updating the comment to mention this subtlety that I forgot, having
written the code. :P
Cc: stable@vger.kernel.org # v6.10
Fixes: 5befb047b9f4de ("xfs: add the ability to reap entire inode forks")
Signed-off-by: Darrick J. Wong <djwong@kernel.org>
Assisted-by: LOLLM # finding obvious bugs
Reviewed-by: Christoph Hellwig <hch@lst.de>
Signed-off-by: Carlos Maiolino <cem@kernel.org>
Diffstat (limited to 'tools/perf/scripts/python/bin/stackcollapse-record')
0 files changed, 0 insertions, 0 deletions