On Mon, Nov 07, 2022 at 05:28:41PM -0800, Darrick J. Wong wrote: > From: Darrick J. Wong <djwong@xxxxxxxxxx> > > 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@xxxxxxxxxx> > --- > v23.3: fix vague wording of comment > v23.2: fix the commit message to discuss what's really going on in this > patch. > --- > fs/xfs/scrub/repair.c | 4 ++-- > 1 file changed, 2 insertions(+), 2 deletions(-) Looks good. Reviewed-by: Dave Chinner <dchinner@xxxxxxxxxx> -- Dave Chinner david@xxxxxxxxxxxxx
