public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Dave Chinner <david@fromorbit.com>
To: Eric Sandeen <sandeen@sandeen.net>
Cc: Ole Tange <tange@binf.ku.dk>, xfs-oss <xfs@oss.sgi.com>
Subject: Re: [PATCH] xfs_repair: skip freelist scan of dodgy agf in no-modify mode
Date: Sat, 2 Mar 2013 12:18:06 +1100	[thread overview]
Message-ID: <20130302011806.GF23616@dastard> (raw)
In-Reply-To: <51313DE8.5080104@sandeen.net>

On Fri, Mar 01, 2013 at 05:46:48PM -0600, Eric Sandeen wrote:
> In no-modify mode (-n), verify_set_agf doesn't fix up bad
> freelist blocks that it finds.  When we get to scan_freelist,
> this can wreak havoc if, for example, first > last and the loop
> never exits; we index agfl->agfl_bno[i] off into the weeds.
> 
> To fix this, re-check the values in no-modify mode, and if
> they're off, warn about it and skip the scan.
> 
> In addition, add a check to verify_set_agf() to ensure that
> first <= last.
> 
> Reported-by: Ole Tange <tange@binf.ku.dk>
> Signed-off-by: Eric Sandeen <sandeen@redhat.com>
> ---
> 
> diff --git a/repair/agheader.c b/repair/agheader.c
> index 769022d..68789fe 100644
> --- a/repair/agheader.c
> +++ b/repair/agheader.c
> @@ -86,6 +86,14 @@ verify_set_agf(xfs_mount_t *mp, xfs_agf_t *agf, xfs_agnumber_t i)
>  	 * check first/last AGF fields.  if need be, lose the free
>  	 * space in the AGFL, we'll reclaim it later.
>  	 */
> +	if (be32_to_cpu(agf->agf_flfirst) > be32_to_cpu(agf->agf_fllast)) {
> +		do_warn(_("flfirst %d in agf %d > fllast %d\n"),
> +			be32_to_cpu(agf->agf_flfirst),
> +			i, be32_to_cpu(agf->agf_fllast));
> +		if (!no_modify)
> +			agf->agf_fllast = agf->agf_flfirst = cpu_to_be32(0);
> +	}

I don't think that test is correct. The free list is circular and is
indexed as a pair of head/tail pointers. Hence flfirst > fllast can
be actually valid. e.g. flcount = 4, flfirst=126, fllast = 2 is a
valid free list.

> +
>  	if (be32_to_cpu(agf->agf_flfirst) >= XFS_AGFL_SIZE(mp))  {
>  		do_warn(_("flfirst %d in agf %d too large (max = %zu)\n"),
>  			be32_to_cpu(agf->agf_flfirst),
> diff --git a/repair/scan.c b/repair/scan.c
> index 5345094..0f83fb4 100644
> --- a/repair/scan.c
> +++ b/repair/scan.c
> @@ -1067,6 +1067,17 @@ scan_freelist(
>  	}
>  	agfl = XFS_BUF_TO_AGFL(agflbuf);
>  	i = be32_to_cpu(agf->agf_flfirst);
> +	if (no_modify) {
> +		/* agf values not sanitized, so double check */
> +		if (i >= XFS_AGFL_SIZE(mp) ||
> +		    be32_to_cpu(agf->agf_fllast) >= XFS_AGFL_SIZE(mp) ||
> +		    i > be32_to_cpu(agf->agf_fllast))
> +			do_warn(_("agf %d freelist blocks bad, skipping scan\n"),

"skipping freelist scan"

> +				i);
> +			return;

Also, you might be missing a set of {} there - that will always
return immediately if no_modify is set....

Cheers,

Dave.
-- 
Dave Chinner
david@fromorbit.com

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

  reply	other threads:[~2013-03-02  1:18 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-01 23:46 [PATCH] xfs_repair: skip freelist scan of dodgy agf in no-modify mode Eric Sandeen
2013-03-02  1:18 ` Dave Chinner [this message]
2013-03-02  1:22   ` Eric Sandeen
2013-03-02 21:23 ` [PATCH V2] xfs_repair: skip freelist scan of corrupt " Eric Sandeen
2013-03-03 23:36   ` Dave Chinner
2013-03-08 20:31   ` Rich Johnston
2013-03-08 20:31     ` Eric Sandeen
2013-03-09  9:00     ` Dave Chinner
2013-03-11 12:20       ` Rich Johnston
2013-03-09 15:00     ` Eric Sandeen

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=20130302011806.GF23616@dastard \
    --to=david@fromorbit.com \
    --cc=sandeen@sandeen.net \
    --cc=tange@binf.ku.dk \
    --cc=xfs@oss.sgi.com \
    /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