From: Hillf Danton <hdanton@sina.com>
To: syzbot <syzbot+5a2250fd91b28106c37b@syzkaller.appspotmail.com>
Cc: linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [mm?] [usb?] WARNING in __alloc_skb (4)
Date: Sat, 20 Sep 2025 08:43:00 +0800 [thread overview]
Message-ID: <20250920004306.7233-1-hdanton@sina.com> (raw)
In-Reply-To: <68af7ed3.a00a0220.2929dc.0004.GAE@google.com>
> Date: Wed, 27 Aug 2025 14:55:31 -0700 [thread overview]
> Hello,
>
> syzbot found the following issue on:
>
> HEAD commit: 7fa4d8dc380f Add linux-next specific files for 20250821
> git tree: linux-next
> console output: https://syzkaller.appspot.com/x/log.txt?x=11fecc42580000
> kernel config: https://syzkaller.appspot.com/x/.config?x=ae76068823a236b3
> dashboard link: https://syzkaller.appspot.com/bug?extid=5a2250fd91b28106c37b
> compiler: Debian clang version 20.1.7 (++20250616065708+6146a88f6049-1~exp1~20250616065826.132), Debian LLD 20.1.7
> syz repro: https://syzkaller.appspot.com/x/repro.syz?x=14c94858580000
> C reproducer: https://syzkaller.appspot.com/x/repro.c?x=108ea7bc580000
#syz test linux-next master
--- x/net/core/skbuff.c
+++ y/net/core/skbuff.c
@@ -657,7 +657,7 @@ struct sk_buff *__alloc_skb(unsigned int
likely(node == NUMA_NO_NODE || node == numa_mem_id()))
skb = napi_skb_cache_get();
else
- skb = kmem_cache_alloc_node(cache, gfp_mask & ~GFP_DMA, node);
+ skb = kmem_cache_alloc_node(cache, gfp_mask & ~(GFP_DMA | __GFP_HIGHMEM), node);
if (unlikely(!skb))
return NULL;
prefetchw(skb);
--
next prev parent reply other threads:[~2025-09-20 0:43 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-27 21:55 [syzbot] [mm?] [usb?] WARNING in __alloc_skb (4) syzbot
2025-09-19 16:04 ` Forwarded: test linux-next 7fa4d8dc380f syzbot
2025-09-20 0:43 ` Hillf Danton [this message]
2025-09-20 1:15 ` [syzbot] [mm?] [usb?] WARNING in __alloc_skb (4) syzbot
2025-09-20 2:55 ` Hillf Danton
2025-09-20 4:48 ` syzbot
2025-09-20 10:59 ` Forwarded: syz test syzbot
2025-09-20 18:55 ` Forwarded: re-test syzbot
[not found] <CAL4kbRPgrQO_QYOGBFGoPEG9OZet-LVSvGDT2+37-uiKRWh0ng@mail.gmail.com>
2025-09-19 17:28 ` [syzbot] [mm?] [usb?] WARNING in __alloc_skb (4) syzbot
[not found] <CAL4kbRMa8snwYuwi4zNjx9bNbrRg=MN+xkadQ=89Dc6URRCOog@mail.gmail.com>
2025-09-20 11:37 ` syzbot
[not found] <CAL4kbRPcgyZtXEGuiAR+dpiqfsawnwyKovtKy_vWEgowF+HDMQ@mail.gmail.com>
2025-09-20 20:09 ` 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=20250920004306.7233-1-hdanton@sina.com \
--to=hdanton@sina.com \
--cc=linux-kernel@vger.kernel.org \
--cc=syzbot+5a2250fd91b28106c37b@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