From: Christoph Hellwig <hch@lst.de>
To: Brian Foster <bfoster@redhat.com>
Cc: linux-fsdevel@vger.kernel.org, linux-xfs@vger.kernel.org,
Christian Brauner <brauner@kernel.org>,
Dave Chinner <dchinner@redhat.com>,
Christoph Hellwig <hch@lst.de>,
"Darrick J . Wong" <djwong@kernel.org>
Subject: Re: [PATCH v2 REPOST] iomap: replace folio_batch allocation with stack allocation
Date: Mon, 8 Dec 2025 14:10:41 +0100 [thread overview]
Message-ID: <20251208131041.GA18331@lst.de> (raw)
In-Reply-To: <20251208124018.362848-1-bfoster@redhat.com>
On Mon, Dec 08, 2025 at 07:40:18AM -0500, Brian Foster wrote:
> Any chance we can get this one pulled in soon? It looks like XFS is
> still getting syzbot lockdep noise for the alloc this patch removes.
> Thanks.
Maybe add a:
Fixes: 395ed1ef0012 ("iomap: optional zero range dirty folio processing")
to make that more clear?
prev parent reply other threads:[~2025-12-08 13:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-08 12:40 [PATCH v2 REPOST] iomap: replace folio_batch allocation with stack allocation Brian Foster
2025-12-08 13:10 ` Christoph Hellwig [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=20251208131041.GA18331@lst.de \
--to=hch@lst.de \
--cc=bfoster@redhat.com \
--cc=brauner@kernel.org \
--cc=dchinner@redhat.com \
--cc=djwong@kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--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