From: Zi Yan <ziy@nvidia.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Alan Stern <stern@rowland.harvard.edu>,
Andrew Morton <akpm@linux-foundation.org>,
syzbot <syzbot+805630f1453e490427fa@syzkaller.appspotmail.com>,
apopple@nvidia.com, byungchul@sk.com, david@kernel.org,
gourry@gourry.net, joshua.hahnjy@gmail.com,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
matthew.brost@intel.com, rakie.kim@sk.com,
syzkaller-bugs@googlegroups.com, ying.huang@linux.alibaba.com,
linux-usb@vger.kernel.org
Subject: Re: [syzbot] [mm?] WARNING in ep_write_iter
Date: Mon, 17 Aug 2026 11:19:23 -0400 [thread overview]
Message-ID: <1ED81A86-22F2-415A-8CC0-7E9B4A4446C2@nvidia.com> (raw)
In-Reply-To: <2026081745-unshaken-retread-d744@gregkh>
On 17 Aug 2026, at 11:06, Greg Kroah-Hartman wrote:
> On Mon, Aug 17, 2026 at 10:34:26AM -0400, Zi Yan wrote:
>> On 17 Aug 2026, at 9:55, Alan Stern wrote:
>>
>>> On Sun, Aug 16, 2026 at 07:42:13PM -0700, Andrew Morton wrote:
>>>> On Sun, 16 Aug 2026 21:47:58 -0400 "Zi Yan" <ziy@nvidia.com> wrote:
>>>>
>>>>>>
>>>>>>>> I prefer Andrew's first suggestion. If the user asks the kernel to copy
>>>>>>>> too much data, just fail -- with no warning.
>>>>>>>
>>>>>>> __GFP_WARN gets rid of all other warnings, even if user asks for a
>>>>>>> reasonable size. Why use such a big hammer?
>>>>>>
>>>>>> Because on many systems, WARN causes the kernel to crash. You don't
>>>>>> want the entire system to crash just because the user asked for more
>>>>>> memory than was available.
>>>>>
>>>>> User asking for more memory that what is available is pretty common and
>>>>> should not trigger a WARN or crash, unless you have panic_on_oom set.
>>>>
>>>> I assume Alan is referring to panic_on_warn.
>>>
>>> Yes.
>>
>> Right. That is why I said “unless you have panic_on_oom set”. So panic_on_warn
>> will not crash the kernel if user asks for more memory than what is available.
>
> Are you sure? It kicks off syzbot, what prevents the oops from
> happening if panic_on_warn is enabled and a warning like this happens?
> Am I missing some code somewhere?
usb’s inode.c uses kmalloc to allocate > order 10 memory, namely >4MB. This
caused the warning.
kmalloc’s doc says:
kmalloc is the normal method of allocating memory
for objects smaller than page size in the kernel.
Shouldn’t usb inode.c use a proper memory allocation API?
>
>>>> Heaven knows how common panic_on_warn usage is. Gemini tells me "There
>>>> is no exact global headcount or precise user metric for how many people
>>>> use panic_on_warn. However, the setting is widely enabled across a few
>>>> billion Android devices and many cloud/server provider host kernels
>>>> where automated failover makes a full reboot preferable to running with
>>>> an unknown warning state".
>>>>
>>>> So I do think that WARNs are more serious than we (mm developers) tend
>>>> to assume.
>>>
>>> I do know that Greg KH has pretty strong feelings about this issue.
>>
>> But the warning here is when kernel user wants buddy allocator to give
>> what it cannot allocate, a page order > MAX_PAGE_ORDER. The warning
>> tells that kernel user please ask for a reasonably sized memory.
>
> And if panic_on_warn is enabled, like it is in billions of Linux
> systems, and a user can trigger it, then you just rebooted the box,
> causing a DoS and a simple way to get a CVE assigned for the problem.
>
>>>> So we just shouldn't permit userspace to trivially trigger a
>>>> page-allocation WARN. Especially if the caller is perfectly capable of
>>>> handling an ENOMEM allocation failure, as appears to be the case with
>>>> usb-gadget.
>>>>
>>>> (Does usb-gadget actually get used by Android? Surely not by cloud
>>>> providers!)
>>>>
>>>> (Can this WARN be triggered by unprivileged userspace? I didn't look,
>>>> this matters a lot).
>>>
>>> I don't think it can. Regardless, even privileged userspace shouldn't
>>> be able to crash the whole system by doing something that ought to
>>> return a harmless error.
>>
>> The issue here is that the inode.c code passes the user input len without
>> checking to page allocator code. Capping that is a minimal requirement
>> to prevent untrusted userspace input getting into trusted kernel space code
>> easily.
>
> But why would inode.c know what the page allocation max is? We have put
kmalloc document says:
kmalloc is the normal method of allocating memory
for objects smaller than page size in the kernel.
> arbitrary bounds in other places where you can cause large allocations
> from userspace (like in usbfs), and if that's needed here, great, we can
> do that too. But don't tie that to the mm core values as those can
> change over time.
But inode.c asks for >4MB memory.
Best Regards,
Yan, Zi
next prev parent reply other threads:[~2026-08-17 15:19 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-16 19:25 syzbot
2026-08-16 20:52 ` Andrew Morton
2026-08-16 21:47 ` Zi Yan
2026-08-16 23:32 ` Alan Stern
2026-08-17 0:13 ` Zi Yan
2026-08-17 1:15 ` Alan Stern
2026-08-17 1:47 ` Zi Yan
2026-08-17 2:42 ` Andrew Morton
2026-08-17 13:55 ` Alan Stern
2026-08-17 14:34 ` Zi Yan
2026-08-17 14:37 ` Zi Yan
2026-08-17 15:06 ` Alan Stern
2026-08-17 15:22 ` Zi Yan
2026-08-17 15:37 ` Alan Stern
2026-08-17 18:45 ` Zi Yan
2026-08-18 3:12 ` Alan Stern
2026-08-18 23:45 ` Zi Yan
2026-08-19 1:30 ` Alan Stern
2026-08-17 15:06 ` Greg Kroah-Hartman
2026-08-17 15:19 ` Zi Yan [this message]
2026-08-17 15:55 ` Greg Kroah-Hartman
2026-08-17 18:51 ` Zi Yan
2026-08-17 20:34 ` John Hubbard
2026-08-20 13:55 ` Zi Yan
2026-08-20 13:59 ` Zi Yan
2026-08-20 14:27 ` Alan Stern
2026-08-21 8:30 ` David Laight
2026-08-21 14:24 ` Zi Yan
2026-08-21 15:13 ` David Laight
2026-08-21 15:31 ` Zi Yan
2026-08-26 10:26 ` Vlastimil Babka (SUSE)
2026-08-17 9:14 ` syzbot
2026-08-17 19:45 ` Zi Yan
2026-08-17 19:59 ` syzbot
2026-08-20 13:15 ` Zi Yan
2026-08-20 13:30 ` syzbot
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=1ED81A86-22F2-415A-8CC0-7E9B4A4446C2@nvidia.com \
--to=ziy@nvidia.com \
--cc=akpm@linux-foundation.org \
--cc=apopple@nvidia.com \
--cc=byungchul@sk.com \
--cc=david@kernel.org \
--cc=gourry@gourry.net \
--cc=gregkh@linuxfoundation.org \
--cc=joshua.hahnjy@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-usb@vger.kernel.org \
--cc=matthew.brost@intel.com \
--cc=rakie.kim@sk.com \
--cc=stern@rowland.harvard.edu \
--cc=syzbot+805630f1453e490427fa@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=ying.huang@linux.alibaba.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
all inboxes | Powered by JetHome®