summaryrefslogtreecommitdiff
path: root/scripts/objdiff
diff options
context:
space:
mode:
authorZi Yan <ziy@nvidia.com>2026-08-20 09:19:12 -0400
committerAndrew Morton <akpm@linux-foundation.org>2026-08-27 22:50:04 -0700
commitae67b0e940a60797cb6c0d05f8d206a2bfac4ef6 (patch)
treebab3e68fbfb17c9505cea189e79682310948e262 /scripts/objdiff
parent3113bff8a8a36dd257b681cf5a72f8067d72efaf (diff)
downloadlinux-next-ae67b0e940a60797cb6c0d05f8d206a2bfac4ef6.tar.gz
linux-next-ae67b0e940a60797cb6c0d05f8d206a2bfac4ef6.zip
USB: gadgetfs: do not WARN about excessively large memory allocations
GadgetFS passes an excessively large user input len to kmalloc and kmalloc gives a WARN (see below for details). Suppress it by passing __GFP_NOWARN to kmalloc used by both ep_write_iter() and ep_read_iter(). Follow the same method as commit 4f2629ea67e72 ("USB: usbfs: Don't WARN about excessively large memory allocations"). kmalloc is used to allocate physically contiguous memory for kernel allocations. For requests larger than KMALLOC_MAX_CACHE_SIZE, kmalloc uses the page allocator and can only support up to KMALLOC_MAX_SIZE. For request sizes bigger than KMALLOC_MAX_SIZE, the page allocator can emit a WARN because kmalloc allocates an order greater than MAX_PAGE_ORDER. Link: https://lore.kernel.org/DKTTMAS94IMH.2C6ERY0ZIVWVZ@nvidia.com Fixes: b3c466ce5129 ("page allocator: do not sanity check order in the fast path") Signed-off-by: Zi Yan <ziy@nvidia.com> Reported-by: syzbot+805630f1453e490427fa@syzkaller.appspotmail.com Closes: https://lore.kernel.org/all/6a820ebc.9ebadd4d.20b15e.001b.GAE@google.com/ Tested-by: syzbot+805630f1453e490427fa@syzkaller.appspotmail.com Acked-by: Alan Stern <stern@rowland.harvard.edu> Acked-by: Vlastimil Babka (SUSE) <vbabka@kernel.org> Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org> Cc: <stable@vger.kernel.org> Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Diffstat (limited to 'scripts/objdiff')
0 files changed, 0 insertions, 0 deletions