From: Jason Gunthorpe <jgg@ziepe.ca>
To: "Vlastimil Babka (SUSE)" <vbabka@kernel.org>
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: Tue, 4 Aug 2026 21:46:19 -0300 [thread overview]
Message-ID: <20260805004619.GA28508@ziepe.ca> (raw)
In-Reply-To: <cad222c7-0ca2-47ba-a21d-1522384713c8@kernel.org>
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.
Jason
next prev parent reply other threads:[~2026-08-05 0:46 UTC|newest]
Thread overview: 11+ 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 [this message]
2026-08-05 8:01 ` Vlastimil Babka (SUSE)
2026-08-06 14:29 ` Liam R. Howlett
2026-08-06 15:48 ` Jason Gunthorpe
2026-08-07 13:19 ` Liam R. Howlett
2026-08-07 19:24 ` Liam R. Howlett
2026-08-07 19:26 ` Jason Gunthorpe
2026-08-07 20:32 ` Liam R. Howlett
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=20260805004619.GA28508@ziepe.ca \
--to=jgg@ziepe.ca \
--cc=akpm@linux-foundation.org \
--cc=jannh@google.com \
--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 \
--cc=vbabka@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.