diff options
| author | Darrick J. Wong <djwong@kernel.org> | 2026-09-09 23:00:16 -0700 |
|---|---|---|
| committer | Carlos Maiolino <cem@kernel.org> | 2026-09-15 10:09:57 +0200 |
| commit | afbccf99f7f82117cba9ad4b0b006692030f49e8 (patch) | |
| tree | d7817a6d8eb777bf301b7175573bac0ac7770d44 /tools/perf/tests/shell/test_stackcollapse_python.sh | |
| parent | 5b644229bd677d52c4efa5973c1fab842c57f896 (diff) | |
| download | linux-next-afbccf99f7f82117cba9ad4b0b006692030f49e8.tar.gz linux-next-afbccf99f7f82117cba9ad4b0b006692030f49e8.zip | |
xfs: don't assert when XFS_SCRUB_TYPE_HEALTHY scans return corruption
XFS_SCRUB_TYPE_HEALTHY is a synthentic scrub type so that xfs_scrub can
tell the kernel "Hey, I finished a scan and saw no problems" and have
the kernel forget that it saw indirect evidence of corruption.
Unfortunately, as LOLLM points out, it's possible for the health system
to record a new corruption just before xfs_scrub gets to
XFS_SCRUB_TYPE_HEALTHY. In this case, the existing logic doesn't return
early and instead wanders into unknown regions of type_to_health_flag
and trips the assert because HEALTHY doesn't have a group assignment.
Fix the logic so that we always return early for a HEALTHY scrub type,
even if we decide not to call xchk_mark_all_healthy.
Cc: stable@vger.kernel.org # v6.9
Fixes: a1f3e0cca41036 ("xfs: update health status if we get a clean bill of health")
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/tests/shell/test_stackcollapse_python.sh')
0 files changed, 0 insertions, 0 deletions
