From: Chandan Babu R <chandanrlinux@gmail.com>
To: "Darrick J. Wong" <darrick.wong@oracle.com>
Cc: linux-xfs@vger.kernel.org, david@fromorbit.com
Subject: Re: [PATCH 4/4] xfs: directory scrub should check the null bestfree entries too
Date: Fri, 13 Nov 2020 14:38:30 +0530 [thread overview]
Message-ID: <23267072.YfSsYFqK8s@garuda> (raw)
In-Reply-To: <160494587794.772802.11043398495774645870.stgit@magnolia>
On Monday 9 November 2020 11:47:58 PM IST Darrick J. Wong wrote:
> From: Darrick J. Wong <darrick.wong@oracle.com>
>
> Teach the directory scrubber to check all the bestfree entries,
> including the null ones. We want to be able to detect the case where
> the entry is null but there actually /is/ a directory data block.
>
> Found by fuzzing lbests[0] = ones in xfs/391.
>
Looks good to me.
Reviewed-by: Chandan Babu R <chandanrlinux@gmail.com>
> Fixes: df481968f33b ("xfs: scrub directory freespace")
> Signed-off-by: Darrick J. Wong <darrick.wong@oracle.com>
> ---
> fs/xfs/scrub/dir.c | 27 ++++++++++++++++++++-------
> 1 file changed, 20 insertions(+), 7 deletions(-)
>
>
> diff --git a/fs/xfs/scrub/dir.c b/fs/xfs/scrub/dir.c
> index 7c432997edad..b045e95c2ea7 100644
> --- a/fs/xfs/scrub/dir.c
> +++ b/fs/xfs/scrub/dir.c
> @@ -558,14 +558,27 @@ xchk_directory_leaf1_bestfree(
> /* Check all the bestfree entries. */
> for (i = 0; i < bestcount; i++, bestp++) {
> best = be16_to_cpu(*bestp);
> + error = xfs_dir3_data_read(sc->tp, sc->ip,
> + xfs_dir2_db_to_da(args->geo, i),
> + XFS_DABUF_MAP_HOLE_OK,
> + &dbp);
> + if (!xchk_fblock_process_error(sc, XFS_DATA_FORK, lblk,
> + &error))
> + break;
> +
> + if (!dbp) {
> + if (best != NULLDATAOFF) {
> + xchk_fblock_set_corrupt(sc, XFS_DATA_FORK,
> + lblk);
> + break;
> + }
> + continue;
> + }
> +
> if (best == NULLDATAOFF)
> - continue;
> - error = xfs_dir3_data_read(sc->tp, sc->ip,
> - i * args->geo->fsbcount, 0, &dbp);
> - if (!xchk_fblock_process_error(sc, XFS_DATA_FORK, lblk,
> - &error))
> - break;
> - xchk_directory_check_freesp(sc, lblk, dbp, best);
> + xchk_fblock_set_corrupt(sc, XFS_DATA_FORK, lblk);
> + else
> + xchk_directory_check_freesp(sc, lblk, dbp, best);
> xfs_trans_brelse(sc->tp, dbp);
> if (sc->sm->sm_flags & XFS_SCRUB_OFLAG_CORRUPT)
> break;
>
>
--
chandan
next prev parent reply other threads:[~2020-11-13 9:08 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-09 18:17 [PATCH 0/4] xfs: fix various scrub problems Darrick J. Wong
2020-11-09 18:17 ` [PATCH 1/4] xfs: fix brainos in the refcount scrubber's rmap fragment processor Darrick J. Wong
2020-11-10 18:35 ` Christoph Hellwig
2020-11-12 12:51 ` Chandan Babu R
2020-11-12 16:05 ` Darrick J. Wong
2020-11-13 5:11 ` Chandan Babu R
2020-11-09 18:17 ` [PATCH 2/4] xfs: fix the minrecs logic when dealing with inode root child blocks Darrick J. Wong
2020-11-13 6:35 ` Chandan Babu R
2020-11-14 10:39 ` Christoph Hellwig
2020-11-09 18:17 ` [PATCH 3/4] xfs: strengthen rmap record flags checking Darrick J. Wong
2020-11-13 7:02 ` Chandan Babu R
2020-11-14 10:40 ` Christoph Hellwig
2020-11-09 18:17 ` [PATCH 4/4] xfs: directory scrub should check the null bestfree entries too Darrick J. Wong
2020-11-13 9:08 ` Chandan Babu R [this message]
2020-11-14 10:40 ` Christoph Hellwig
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=23267072.YfSsYFqK8s@garuda \
--to=chandanrlinux@gmail.com \
--cc=darrick.wong@oracle.com \
--cc=david@fromorbit.com \
--cc=linux-xfs@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox