public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: "Darrick J. Wong" <djwong@kernel.org>
To: Dave Chinner <david@fromorbit.com>
Cc: linux-xfs@vger.kernel.org
Subject: Re: [PATCH 2/2] xfs: online checking of the free rt extent count
Date: Fri, 14 Oct 2022 14:46:13 -0700	[thread overview]
Message-ID: <Y0nYpaNkPRgVE+LX@magnolia> (raw)
In-Reply-To: <20221014035634.GM3600936@dread.disaster.area>

On Fri, Oct 14, 2022 at 02:56:34PM +1100, Dave Chinner wrote:
> On Sun, Oct 02, 2022 at 11:20:05AM -0700, Darrick J. Wong wrote:
> > From: Darrick J. Wong <djwong@kernel.org>
> > 
> > Teach the summary count checker to count the number of free realtime
> > extents and compare that to the superblock copy.
> > 
> > Signed-off-by: Darrick J. Wong <djwong@kernel.org>
> > ---
> >  fs/xfs/scrub/fscounters.c |   86 ++++++++++++++++++++++++++++++++++++++++++++-
> >  fs/xfs/scrub/scrub.h      |    8 ----
> >  2 files changed, 84 insertions(+), 10 deletions(-)
> 
> .....
> > @@ -288,6 +301,59 @@ xchk_fscount_aggregate_agcounts(
> >  	return 0;
> >  }
> >  
> > +#ifdef CONFIG_XFS_RT
> > +static inline int
> > +xchk_fscount_add_frextent(
> > +	struct xfs_mount		*mp,
> > +	struct xfs_trans		*tp,
> > +	const struct xfs_rtalloc_rec	*rec,
> > +	void				*priv)
> 
> This is a callback function, so it shouldn't be declared as
> "inline"....

Ok done.

--D

> With that fixed,
> 
> Reviewed-by: Dave Chinner <dchinner@redhat.com>
> 
> -- 
> Dave Chinner
> david@fromorbit.com

      reply	other threads:[~2022-10-14 21:47 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-02 18:20 [PATCHSET v23.1 0/2] xfs: enhance fs summary counter scrubber Darrick J. Wong
2022-10-02 18:20 ` [PATCH 1/2] xfs: skip fscounters comparisons when the scan is incomplete Darrick J. Wong
2022-10-14  3:51   ` Dave Chinner
2022-10-02 18:20 ` [PATCH 2/2] xfs: online checking of the free rt extent count Darrick J. Wong
2022-10-14  3:56   ` Dave Chinner
2022-10-14 21:46     ` Darrick J. Wong [this message]

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=Y0nYpaNkPRgVE+LX@magnolia \
    --to=djwong@kernel.org \
    --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