diff options
| author | Darrick J. Wong <djwong@kernel.org> | 2022-07-14 11:05:44 -0700 |
|---|---|---|
| committer | Darrick J. Wong <djwong@kernel.org> | 2022-11-09 19:07:11 -0800 |
| commit | 83d4a9b26011203f89b27637a1e2410272e7c6ba (patch) | |
| tree | 6dea811255657f84e247b9fdf97da371ffa0c015 /kernel/irq_work.c | |
| parent | 362005d01feaba9096dcf2015f69bac25d4e5555 (diff) | |
xfs: don't return -EFSCORRUPTED from repair when resources cannot be grabbedxfs-6.2-fixes_2022-11-09
If we tried to repair something but the repair failed with -EDEADLOCK,
that means that the repair function couldn't grab some resource it
needed and wants us to try again. If we try again (with TRY_HARDER) but
still can't get all the resources we need, the repair fails and errors
remain on the filesystem.
Right now, repair returns the -EDEADLOCK to the caller as -EFSCORRUPTED,
which results in XFS_SCRUB_OFLAG_CORRUPT being passed out to userspace.
This is not correct because repair has not determined that anything is
corrupt. If the repair had been invoked on an object that could be
optimized but wasn't corrupt (OFLAG_PREEN), the inability to grab
resources will be reported to userspace as corrupt metadata, and users
will be unnecessarily alarmed that their suboptimal metadata turned into
a corruption.
Fix this by returning zero so that the results of the actual scrub will
be copied back out to userspace.
Signed-off-by: Darrick J. Wong <djwong@kernel.org>
Diffstat (limited to 'kernel/irq_work.c')
0 files changed, 0 insertions, 0 deletions