From: Christoph Hellwig <hch@lst.de>
To: "Darrick J. Wong" <djwong@kernel.org>
Cc: Christoph Hellwig <hch@lst.de>, Carlos Maiolino <cem@kernel.org>,
Dave Chinner <dchinner@redhat.com>,
linux-xfs@vger.kernel.org,
syzbot+0391d34e801643e2809b@syzkaller.appspotmail.com
Subject: Re: [PATCH 3/3] xfs: switch (back) to a per-buftarg buffer hash
Date: Tue, 20 Jan 2026 08:06:15 +0100 [thread overview]
Message-ID: <20260120070615.GB3954@lst.de> (raw)
In-Reply-To: <20260120023918.GG15551@frogsfrogsfrogs>
On Mon, Jan 19, 2026 at 06:39:18PM -0800, Darrick J. Wong wrote:
> On Mon, Jan 19, 2026 at 04:31:37PM +0100, Christoph Hellwig wrote:
> > The per-AG buffer hashes were added when all buffer lookups took a
> > per-hash look. Since then we've made lookups entirely lockless and
> > removed the need for a hash-wide lock for inserts and removals as
> > well. With this there is no need to sharding the hash, so reduce the
> > used resources by using a per-buftarg hash for all buftargs.
>
> Hey, not having all the per-ag buffer cache sounds neat!
>
> > Long after writing this initially, syzbot found a problem in the
> > buffer cache teardown order, which this happens to fix as well.
>
> What did we get wrong, specifically?
Dave has a really good analysis here:
https://lore.kernel.org/linux-xfs/aLeUdemAZ5wmtZel@dread.disaster.area/
> Also: Is there a simpler fix for this bug that we can stuff into old lts
> kernels?
I can't really think of anything much simpler, just different. It would
require some careful reordering of the unmount path, which is always
hairy.
> Or is this fix independent of the b_hold and lockref changes
> in the previous patches?
In theory it is, except that the old tricks with the refcount would
make it very difficult. I tried to reorder this twice and failed
both times.
next prev parent reply other threads:[~2026-01-20 7:06 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-19 15:31 buffer cache simplification Christoph Hellwig
2026-01-19 15:31 ` [PATCH 1/3] xfs: don't keep a reference for buffers on the LRU Christoph Hellwig
2026-01-20 2:53 ` Darrick J. Wong
2026-01-20 6:55 ` Christoph Hellwig
2026-01-19 15:31 ` [PATCH 2/3] xfs: use a lockref for the buffer reference count Christoph Hellwig
2026-01-20 2:53 ` Darrick J. Wong
2026-01-19 15:31 ` [PATCH 3/3] xfs: switch (back) to a per-buftarg buffer hash Christoph Hellwig
2026-01-20 2:39 ` Darrick J. Wong
2026-01-20 7:06 ` Christoph Hellwig [this message]
2026-01-20 15:50 ` Darrick J. Wong
-- strict thread matches above, loose matches on Subject: below --
2026-01-22 5:26 buffer cache simplification v2 Christoph Hellwig
2026-01-22 5:26 ` [PATCH 3/3] xfs: switch (back) to a per-buftarg buffer hash Christoph Hellwig
2026-01-22 18:10 ` Darrick J. Wong
2026-01-23 5:36 ` Christoph Hellwig
2026-01-23 7:01 ` Darrick J. Wong
2026-01-26 5:37 buffer cache simplification v3 Christoph Hellwig
2026-01-26 5:38 ` [PATCH 3/3] xfs: switch (back) to a per-buftarg buffer hash 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=20260120070615.GB3954@lst.de \
--to=hch@lst.de \
--cc=cem@kernel.org \
--cc=dchinner@redhat.com \
--cc=djwong@kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=syzbot+0391d34e801643e2809b@syzkaller.appspotmail.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