From: Niklas Cassel <cassel@kernel.org>
To: Christoph Hellwig <hch@lst.de>
Cc: cem@kernel.org, dlemoal@kernel.org, hans.holmberg@wdc.com,
linux-xfs@vger.kernel.org
Subject: Re: [PATCH] xfs: fix number of GC bvecs
Date: Thu, 2 Apr 2026 20:49:58 +0200 [thread overview]
Message-ID: <ac66VqtCGW89S6XN@ryzen> (raw)
In-Reply-To: <20260401135801.124987-1-hch@lst.de>
Hello Christoph,
On Wed, Apr 01, 2026 at 03:58:01PM +0200, Christoph Hellwig wrote:
> GC scratch allocations can wrap around and use the same buffer twice, and
> the current code fails to account for that. So far this worked due to
> rounding in the block layer, but changes to the bio allocator drop the
Which change in the bio allocator?
If it is a commit that has landed already, I think it would be nice to
mention the commit in the usual "commit + 12 character SHA1" format.
If it is a change in a series that has not landed yet, it would be nice
if you could provide a link to the series, e.g. after the commit log
(after the "---").
Kind regards,
Niklas
next prev parent reply other threads:[~2026-04-02 18:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-01 13:58 [PATCH] xfs: fix number of GC bvecs Christoph Hellwig
2026-04-01 19:47 ` Damien Le Moal
2026-04-02 7:25 ` Hans Holmberg
2026-04-06 5:51 ` Christoph Hellwig
2026-04-02 18:49 ` Niklas Cassel [this message]
2026-04-06 5:52 ` 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=ac66VqtCGW89S6XN@ryzen \
--to=cassel@kernel.org \
--cc=cem@kernel.org \
--cc=dlemoal@kernel.org \
--cc=hans.holmberg@wdc.com \
--cc=hch@lst.de \
--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