From: Matthew Wilcox <willy@infradead.org>
To: lsf-pc@lists.linux-foundation.org, linux-mm@kvack.org,
linux-fsdevel@vger.kernel.org
Cc: "Theodore Y. Ts'o" <tytso@mit.edu>, Chris Mason <clm@fb.com>,
Josef Bacik <josef@toxicpanda.com>,
Luis Chamberlain <mcgrof@kernel.org>
Subject: [LSF/MM/BPF Topic] Filesystem reclaim & memory allocation BOF
Date: Wed, 26 Mar 2025 15:25:07 +0000 [thread overview]
Message-ID: <Z-QcUwDHHfAXl9mK@casper.infradead.org> (raw)
We've got three reports now (two are syzkaller kiddie stuff, but one's a
real workload) of a warning in the page allocator from filesystems
doing reclaim. Essentially they're using GFP_NOFAIL from reclaim
context. This got me thinking about bs>PS and I realised that if we fix
this, then we're going to end up trying to do high order GFP_NOFAIL allocations
in the memory reclaim path, and that is really no bueno.
https://lore.kernel.org/linux-mm/20250326105914.3803197-1-matt@readmodwrite.com/
I'll prepare a better explainer of the problem in advance of this. It
looks like we have a slot at 17:30 today?
Required attendees: Ted, Luis, Chris, Josef, other people who've wrestled
with this before.
next reply other threads:[~2025-03-26 15:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-26 15:25 Matthew Wilcox [this message]
2025-03-26 15:55 ` Theodore Ts'o
2025-03-26 16:19 ` Matthew Wilcox
2025-03-26 17:47 ` [Lsf-pc] " Jan Kara
2025-03-26 19:08 ` Chris Mason
2025-03-26 21:48 ` Dave Chinner
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=Z-QcUwDHHfAXl9mK@casper.infradead.org \
--to=willy@infradead.org \
--cc=clm@fb.com \
--cc=josef@toxicpanda.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lsf-pc@lists.linux-foundation.org \
--cc=mcgrof@kernel.org \
--cc=tytso@mit.edu \
/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