From: syzbot <syzbot+5a2250fd91b28106c37b@syzkaller.appspotmail.com>
To: kriish.sharma2006@gmail.com, linux-kernel@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [mm?] [usb?] WARNING in __alloc_skb (4)
Date: Fri, 19 Sep 2025 10:28:02 -0700 [thread overview]
Message-ID: <68cd92a2.050a0220.13cd81.0006.GAE@google.com> (raw)
In-Reply-To: <CAL4kbRPgrQO_QYOGBFGoPEG9OZet-LVSvGDT2+37-uiKRWh0ng@mail.gmail.com>
Hello,
syzbot has tested the proposed patch but the reproducer is still triggering an issue:
WARNING in __alloc_skb
------------[ cut here ]------------
WARNING: mm/page_alloc.c:5124 at __alloc_frozen_pages_noprof+0x2c8/0x370 mm/page_alloc.c:5124, CPU#0: dhcpcd/5533
Modules linked in:
CPU: 0 UID: 0 PID: 5533 Comm: dhcpcd Not tainted syzkaller #0 PREEMPT(full)
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 08/18/2025
RIP: 0010:__alloc_frozen_pages_noprof+0x2c8/0x370 mm/page_alloc.c:5124
Code: 74 10 4c 89 e7 89 54 24 0c e8 f4 11 0d 00 8b 54 24 0c 49 83 3c 24 00 0f 85 a5 fe ff ff e9 a6 fe ff ff c6 05 fe aa b7 0d 01 90 <0f> 0b 90 e9 18 ff ff ff a9 00 00 08 00 48 8b 4c 24 10 4c 8d 44 24
RSP: 0018:ffffc90000007780 EFLAGS: 00010246
RAX: ffffc90000007700 RBX: 0000000000000014 RCX: 0000000000000000
RDX: 0000000000000000 RSI: 0000000000000000 RDI: ffffc900000077e8
RBP: ffffc90000007870 R08: ffffc900000077e7 R09: 0000000000000000
R10: ffffc900000077c0 R11: fffff52000000efd R12: 0000000000000000
R13: 1ffff92000000ef4 R14: 0000000000060820 R15: dffffc0000000000
FS: 00007f76a8485740(0000) GS:ffff8881257c4000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 000056268ae52138 CR3: 0000000032510000 CR4: 00000000003526f0
Call Trace:
<IRQ>
alloc_pages_mpol+0x232/0x4a0 mm/mempolicy.c:2416
___kmalloc_large_node+0x5f/0x1b0 mm/slub.c:4306
__kmalloc_large_node_noprof+0x18/0x90 mm/slub.c:4337
__do_kmalloc_node mm/slub.c:4353 [inline]
__kmalloc_node_track_caller_noprof+0x34d/0x4a0 mm/slub.c:4384
kmalloc_reserve+0x1b8/0x290 net/core/skbuff.c:608
__alloc_skb+0x142/0x2d0 net/core/skbuff.c:669
__netdev_alloc_skb+0x108/0x970 net/core/skbuff.c:733
rx_submit+0x100/0xab0 drivers/net/usb/usbnet.c:-1
rx_alloc_submit+0xa6/0x140 drivers/net/usb/usbnet.c:1538
usbnet_bh+0x9a5/0xd70 drivers/net/usb/usbnet.c:1607
process_one_work kernel/workqueue.c:3236 [inline]
process_scheduled_works+0xae1/0x17b0 kernel/workqueue.c:3319
bh_worker+0x2b1/0x600 kernel/workqueue.c:3579
tasklet_action+0xc/0x70 kernel/softirq.c:854
handle_softirqs+0x283/0x870 kernel/softirq.c:579
do_softirq+0xec/0x180 kernel/softirq.c:480
</IRQ>
<TASK>
__local_bh_enable_ip+0x17d/0x1c0 kernel/softirq.c:407
__dev_open+0x694/0x880 net/core/dev.c:1690
__dev_change_flags+0x1ea/0x6d0 net/core/dev.c:9549
netif_change_flags+0x88/0x1a0 net/core/dev.c:9612
dev_change_flags+0x130/0x260 net/core/dev_api.c:68
devinet_ioctl+0xbb4/0x1b50 net/ipv4/devinet.c:1200
inet_ioctl+0x3c0/0x4c0 net/ipv4/af_inet.c:1001
sock_do_ioctl+0xd9/0x300 net/socket.c:1238
sock_ioctl+0x576/0x790 net/socket.c:1359
vfs_ioctl fs/ioctl.c:51 [inline]
__do_sys_ioctl fs/ioctl.c:598 [inline]
__se_sys_ioctl+0xf9/0x170 fs/ioctl.c:584
do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
do_syscall_64+0xfa/0xfa0 arch/x86/entry/syscall_64.c:94
entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7f76a8585378
Code: 00 00 48 8d 44 24 08 48 89 54 24 e0 48 89 44 24 c0 48 8d 44 24 d0 48 89 44 24 c8 b8 10 00 00 00 c7 44 24 b8 10 00 00 00 0f 05 <89> c2 3d 00 f0 ff ff 77 07 89 d0 c3 0f 1f 40 00 48 8b 15 49 3a 0d
RSP: 002b:00007ffd0f936168 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
RAX: ffffffffffffffda RBX: 0000000000000012 RCX: 00007f76a8585378
RDX: 00007ffd0f946360 RSI: 0000000000008914 RDI: 0000000000000012
RBP: 0000000000000000 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 00007ffd0f956500
R13: 00007f76a84856c8 R14: 0000000000000028 R15: 0000000000008914
</TASK>
Tested on:
commit: 7fa4d8dc Add linux-next specific files for 20250821
git tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/
console output: https://syzkaller.appspot.com/x/log.txt?x=115a1858580000
kernel config: https://syzkaller.appspot.com/x/.config?x=53aaf18b1b202211
dashboard link: https://syzkaller.appspot.com/bug?extid=5a2250fd91b28106c37b
compiler: Debian clang version 20.1.8 (++20250708063551+0c9f909b7976-1~exp1~20250708183702.136), Debian LLD 20.1.8
Note: no patches were applied.
next parent reply other threads:[~2025-09-19 17:28 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAL4kbRPgrQO_QYOGBFGoPEG9OZet-LVSvGDT2+37-uiKRWh0ng@mail.gmail.com>
2025-09-19 17:28 ` syzbot [this message]
[not found] <CAL4kbRPcgyZtXEGuiAR+dpiqfsawnwyKovtKy_vWEgowF+HDMQ@mail.gmail.com>
2025-09-20 20:09 ` [syzbot] [mm?] [usb?] WARNING in __alloc_skb (4) syzbot
[not found] <CAL4kbRMa8snwYuwi4zNjx9bNbrRg=MN+xkadQ=89Dc6URRCOog@mail.gmail.com>
2025-09-20 11:37 ` syzbot
2025-08-27 21:55 syzbot
2025-09-20 0:43 ` Hillf Danton
2025-09-20 1:15 ` syzbot
2025-09-20 2:55 ` Hillf Danton
2025-09-20 4:48 ` 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=68cd92a2.050a0220.13cd81.0006.GAE@google.com \
--to=syzbot+5a2250fd91b28106c37b@syzkaller.appspotmail.com \
--cc=kriish.sharma2006@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--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