Linux XFS filesystem development
 help / color / mirror / Atom feed
From: Carlos Maiolino <cem@kernel.org>
To: "Darrick J. Wong" <djwong@kernel.org>
Cc: Eric Sandeen <sandeen@sandeen.net>,
	 Christoph Hellwig <hch@infradead.org>,
	Eric Sandeen <sandeen@redhat.com>,
	linux-xfs@vger.kernel.org
Subject: Re: [PATCH 3/3] xfs: re-use refcount scrub/repair code for rtrefcount
Date: Thu, 8 Oct 2026 13:15:29 +0200	[thread overview]
Message-ID: <asd6ChmrXw4UWku6@cronus.toxiclabs.cc> (raw)
In-Reply-To: <20261007153757.GC2705364@frogsfrogsfrogs>

On Wed, Oct 07, 2026 at 08:37:57AM -0700, Darrick J. Wong wrote:
> On Wed, Oct 07, 2026 at 10:32:20AM -0500, Eric Sandeen wrote:
> > On 10/7/26 8:51 AM, Christoph Hellwig wrote:
> > > On Fri, Oct 02, 2026 at 04:08:11PM -0500, Eric Sandeen wrote:
> > >> Some code in scrub/rtrefcount.c is copied from scrub/refcount.c; it
> > >> differs only in function & structure names and a couple types and
> > >> macros, which share the same underlying types and values.
> > >>
> > >> Similarly for code in fs/xfs/scrub/[rt]refcount_repair.c
> > >>
> > >> Export the refcount versions, use them for rtrefcount scrubbing,
> > > 
> > > Not really an export fortunately :)
> > 
> > Oh, uh, yeah. I didn't mean like EXPORT_SYMBOL just un-STATIC. :( 
> > 
> > Maybe Carlos fix it to:
> > 
> > Make the refcount versions non-static and use them for rtrefcount scrubbing.

yup, no big deal.

> > 
> > on commit, or I can send another version if needed.
> 
> s/Export/Share/ ?

I went Eric's way, at least looked better for my taste. If you have
any objections, let me know.

> 
> --D
> 
> > > 
> > >> eliminate the copies, and add build-time asserts so that the type/value
> > >> matches mentioned above do not drift.
> > > 
> > >>  5 files changed, 72 insertions(+), 316 deletions(-)
> > > 
> > > Nice code savings!
> > > 
> > > Looks good modulo the commit log nitpick:
> > > 
> > > Reviewed-by: Christoph Hellwig <hch@lst.de>
> > > 
> > 
> > Thanks,
> > -Eric
> > 
> 

  reply	other threads:[~2026-10-08 11:15 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-02 21:08 [PATCH 0/3] xfs: more misc code deduplication Eric Sandeen
2026-10-02 21:08 ` [PATCH 1/3] xfs: factor out xfs_dir2_sf_copy_entries helper Eric Sandeen
2026-10-05 12:14   ` Carlos Maiolino
2026-10-07 13:50   ` Christoph Hellwig
2026-10-02 21:08 ` [PATCH 2/3] xfs: factor out xrep_reset_fork_to_extents helper for scrub/repair Eric Sandeen
2026-10-05 13:07   ` Carlos Maiolino
2026-10-05 14:12     ` Eric Sandeen
2026-10-05 19:11   ` [PATCH V2 " Eric Sandeen
2026-10-05 20:20     ` Darrick J. Wong
2026-10-05 20:43       ` Eric Sandeen
2026-10-05 21:17         ` Darrick J. Wong
2026-10-06  8:32           ` Carlos Maiolino
2026-10-07 13:52             ` Christoph Hellwig
2026-10-07 15:25     ` [PATCH V3 " Eric Sandeen
2026-10-08 11:02       ` Carlos Maiolino
2026-10-02 21:08 ` [PATCH 3/3] xfs: re-use refcount scrub/repair code for rtrefcount Eric Sandeen
2026-10-05 20:38   ` Darrick J. Wong
2026-10-06  8:25   ` Carlos Maiolino
2026-10-07 13:51   ` Christoph Hellwig
2026-10-07 15:32     ` Eric Sandeen
2026-10-07 15:37       ` Darrick J. Wong
2026-10-08 11:15         ` Carlos Maiolino [this message]
2026-10-08 11:09   ` Carlos Maiolino
2026-10-08 13:32 ` [PATCH 0/3] xfs: more misc code deduplication Carlos Maiolino

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=asd6ChmrXw4UWku6@cronus.toxiclabs.cc \
    --to=cem@kernel.org \
    --cc=djwong@kernel.org \
    --cc=hch@infradead.org \
    --cc=linux-xfs@vger.kernel.org \
    --cc=sandeen@redhat.com \
    --cc=sandeen@sandeen.net \
    /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