From: "Vlastimil Babka (SUSE)" <vbabka@kernel.org>
To: Jason Gunthorpe <jgg@ziepe.ca>
Cc: "Liam R. Howlett" <liam@infradead.org>,
syzbot <syzbot+78a7af91b68fc6394771@syzkaller.appspotmail.com>,
akpm@linux-foundation.org, jannh@google.com,
linux-kernel@vger.kernel.org, linux-mm@kvack.org, ljs@kernel.org,
pfalcato@suse.de, syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [mm?] WARNING in mas_nomem
Date: Wed, 5 Aug 2026 10:01:16 +0200 [thread overview]
Message-ID: <5cf3542f-fca7-44d0-8a17-8aa316b1fb12@kernel.org> (raw)
In-Reply-To: <20260805004619.GA28508@ziepe.ca>
On 8/5/26 02:46, Jason Gunthorpe wrote:
> On Fri, Jul 31, 2026 at 06:07:24PM +0200, Vlastimil Babka (SUSE) wrote:
>
>> > Thanks to Vlastimil and Pedro for the help on the plan.
>> >
>> > Summary of previous conversation is here:
>> > https://lore.kernel.org/all/20260618152451.GE231643@ziepe.ca/
>>
>> Yeah, unfortunately, "too small to fail" is a lie, because in some cases it
>> can fail (such as the task itself becoming oom killer victim) or any of the
>> other conditions that can cause __alloc_pages_may_oom() return with
>> *did_some_progress == 0.
>
> But then we are back to the original problem, an erase API that can
> fail is fundamentally broken.
That's why the plan is to add __GFP_NOFAIL, which overrides the
possibilities to fail listed above.
> Jason
next prev parent reply other threads:[~2026-08-05 8:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-31 7:30 [syzbot] [mm?] WARNING in mas_nomem syzbot
2026-07-31 15:59 ` Liam R. Howlett
2026-07-31 16:07 ` Vlastimil Babka (SUSE)
2026-08-05 0:46 ` Jason Gunthorpe
2026-08-05 8:01 ` Vlastimil Babka (SUSE) [this message]
2026-08-06 14:29 ` Liam R. Howlett
2026-08-06 15:48 ` Jason Gunthorpe
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=5cf3542f-fca7-44d0-8a17-8aa316b1fb12@kernel.org \
--to=vbabka@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=jannh@google.com \
--cc=jgg@ziepe.ca \
--cc=liam@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=ljs@kernel.org \
--cc=pfalcato@suse.de \
--cc=syzbot+78a7af91b68fc6394771@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.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