* [syzbot] [mm?] [usb?] WARNING in __alloc_skb (4)
@ 2025-08-27 21:55 syzbot
2025-09-20 0:43 ` Hillf Danton
2025-09-20 2:55 ` Hillf Danton
0 siblings, 2 replies; 8+ messages in thread
From: syzbot @ 2025-08-27 21:55 UTC (permalink / raw)
To: akpm, apopple, byungchul, david, gourry, joshua.hahnjy,
linux-kernel, linux-mm, linux-usb, matthew.brost, rakie.kim,
syzkaller-bugs, ying.huang, ziy
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
Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/63178c6ef3f8/disk-7fa4d8dc.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/c5c27b0841e0/vmlinux-7fa4d8dc.xz
kernel image: https://storage.googleapis.com/syzbot-assets/9a8832715cca/bzImage-7fa4d8dc.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+5a2250fd91b28106c37b@syzkaller.appspotmail.com
------------[ cut here ]------------
WARNING: mm/page_alloc.c:5124 at __alloc_frozen_pages_noprof+0x2c8/0x370 mm/page_alloc.c:5124, CPU#0: dhcpcd/5530
Modules linked in:
CPU: 0 UID: 0 PID: 5530 Comm: dhcpcd Not tainted syzkaller #0 PREEMPT(full)
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/12/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: 00007f4fd75a9740(0000) GS:ffff8881257c4000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007ffebb07e018 CR3: 000000001dadc000 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:0x7f4fd76a9378
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:00007ffc26f40168 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
RAX: ffffffffffffffda RBX: 0000000000000016 RCX: 00007f4fd76a9378
RDX: 00007ffc26f50360 RSI: 0000000000008914 RDI: 0000000000000016
RBP: 0000000000000000 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 00007ffc26f60500
R13: 00007f4fd75a96c8 R14: 0000000000000028 R15: 0000000000008914
</TASK>
---
This report is generated by a bot. It may contain errors.
See https://goo.gl/tpsmEJ for more information about syzbot.
syzbot engineers can be reached at syzkaller@googlegroups.com.
syzbot will keep track of this issue. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.
If the report is already addressed, let syzbot know by replying with:
#syz fix: exact-commit-title
If you want syzbot to run the reproducer, reply with:
#syz test: git://repo/address.git branch-or-commit-hash
If you attach or paste a git patch, syzbot will apply it before testing.
If you want to overwrite report's subsystems, reply with:
#syz set subsystems: new-subsystem
(See the list of subsystem names on the web dashboard)
If the report is a duplicate of another one, reply with:
#syz dup: exact-subject-of-another-report
If you want to undo deduplication, reply with:
#syz undup
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: [syzbot] [mm?] [usb?] WARNING in __alloc_skb (4)
[not found] <CAL4kbRPgrQO_QYOGBFGoPEG9OZet-LVSvGDT2+37-uiKRWh0ng@mail.gmail.com>
@ 2025-09-19 17:28 ` syzbot
0 siblings, 0 replies; 8+ messages in thread
From: syzbot @ 2025-09-19 17:28 UTC (permalink / raw)
To: kriish.sharma2006, linux-kernel, syzkaller-bugs
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.
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: [syzbot] [mm?] [usb?] WARNING in __alloc_skb (4)
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
1 sibling, 1 reply; 8+ messages in thread
From: Hillf Danton @ 2025-09-20 0:43 UTC (permalink / raw)
To: syzbot; +Cc: linux-kernel, syzkaller-bugs
> 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);
--
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: [syzbot] [mm?] [usb?] WARNING in __alloc_skb (4)
2025-09-20 0:43 ` Hillf Danton
@ 2025-09-20 1:15 ` syzbot
0 siblings, 0 replies; 8+ messages in thread
From: syzbot @ 2025-09-20 1:15 UTC (permalink / raw)
To: hdanton, linux-kernel, syzkaller-bugs
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:5135 at __alloc_frozen_pages_noprof+0x2c8/0x370 mm/page_alloc.c:5135, CPU#1: dhcpcd/5527
Modules linked in:
CPU: 1 UID: 0 PID: 5527 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:5135
Code: 74 10 4c 89 e7 89 54 24 0c e8 f4 b7 0d 00 8b 54 24 0c 49 83 3c 24 00 0f 85 a5 fe ff ff e9 a6 fe ff ff c6 05 25 c9 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:ffffc90000a086e0 EFLAGS: 00010246
RAX: ffffc90000a08700 RBX: 0000000000000014 RCX: 0000000000000000
RDX: 0000000000000000 RSI: 0000000000000000 RDI: ffffc90000a08748
RBP: ffffc90000a087c8 R08: ffffc90000a08747 R09: 0000000000000000
R10: ffffc90000a08720 R11: fffff520001410e9 R12: 0000000000000000
R13: 1ffff920001410e0 R14: 0000000000060820 R15: dffffc0000000000
FS: 00007f141af9a740(0000) GS:ffff8881258a2000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 000055fc915d6138 CR3: 000000007caf0000 CR4: 00000000003526f0
Call Trace:
<IRQ>
alloc_pages_mpol+0x232/0x4a0 mm/mempolicy.c:2416
___kmalloc_large_node+0x5f/0x1b0 mm/slub.c:5543
__kmalloc_large_node_noprof+0x18/0x90 mm/slub.c:5574
__do_kmalloc_node mm/slub.c:5590 [inline]
__kmalloc_node_track_caller_noprof+0x133/0x800 mm/slub.c:5711
kmalloc_reserve+0x1b8/0x290 net/core/skbuff.c:609
__alloc_skb+0x142/0x2d0 net/core/skbuff.c:670
__netdev_alloc_skb+0x108/0x970 net/core/skbuff.c:734
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:3263 [inline]
process_scheduled_works+0xae1/0x17b0 kernel/workqueue.c:3346
bh_worker+0x2b1/0x600 kernel/workqueue.c:3607
tasklet_action+0xc/0x70 kernel/softirq.c:952
handle_softirqs+0x286/0x870 kernel/softirq.c:622
__do_softirq kernel/softirq.c:656 [inline]
invoke_softirq kernel/softirq.c:496 [inline]
__irq_exit_rcu+0xca/0x1f0 kernel/softirq.c:723
irq_exit_rcu+0x9/0x30 kernel/softirq.c:739
instr_sysvec_apic_timer_interrupt arch/x86/kernel/apic/apic.c:1052 [inline]
sysvec_apic_timer_interrupt+0xa6/0xc0 arch/x86/kernel/apic/apic.c:1052
</IRQ>
<TASK>
asm_sysvec_apic_timer_interrupt+0x1a/0x20 arch/x86/include/asm/idtentry.h:697
RIP: 0010:queue_work_on+0x1f7/0x270 kernel/workqueue.c:2397
Code: 4d 85 ff 75 16 e8 b9 ce 35 00 eb 15 e8 b2 ce 35 00 e8 9d 57 03 0a 4d 85 ff 74 ea e8 a3 ce 35 00 fb 48 c7 44 24 40 0e 36 e0 45 <4b> c7 04 2e 00 00 00 00 66 43 c7 44 2e 09 00 00 43 c6 44 2e 0b 00
RSP: 0018:ffffc900034a7600 EFLAGS: 00000293
RAX: ffffffff818a4a7d RBX: ffff8880560d9201 RCX: ffff88802eb3bc80
RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000
RBP: ffffc900034a76f8 R08: ffffffff8fe4db77 R09: 1ffffffff1fc9b6e
R10: dffffc0000000000 R11: fffffbfff1fc9b6f R12: 0000000000000000
R13: dffffc0000000000 R14: 1ffff92000694ec8 R15: 0000000000000200
queue_work include/linux/workqueue.h:669 [inline]
usbnet_open+0x5c6/0xce0 drivers/net/usb/usbnet.c:958
__dev_open+0x470/0x880 net/core/dev.c:1682
__dev_change_flags+0x1ea/0x6d0 net/core/dev.c:9630
netif_change_flags+0x88/0x1a0 net/core/dev.c:9693
dev_change_flags+0x130/0x260 net/core/dev_api.c:68
devinet_ioctl+0xbb4/0x1b50 net/ipv4/devinet.c:1199
inet_ioctl+0x3c0/0x4c0 net/ipv4/af_inet.c:1003
sock_do_ioctl+0xdc/0x300 net/socket.c:1241
sock_ioctl+0x576/0x790 net/socket.c:1362
vfs_ioctl fs/ioctl.c:51 [inline]
__do_sys_ioctl fs/ioctl.c:597 [inline]
__se_sys_ioctl+0xfc/0x170 fs/ioctl.c:583
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:0x7f141b09a378
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:00007fff3eacfd18 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
RAX: ffffffffffffffda RBX: 0000000000000012 RCX: 00007f141b09a378
RDX: 00007fff3eadff10 RSI: 0000000000008914 RDI: 0000000000000012
RBP: 0000000000000000 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 00007fff3eaf00b0
R13: 00007f141af9a6c8 R14: 0000000000000028 R15: 0000000000008914
</TASK>
----------------
Code disassembly (best guess):
0: 4d 85 ff test %r15,%r15
3: 75 16 jne 0x1b
5: e8 b9 ce 35 00 call 0x35cec3
a: eb 15 jmp 0x21
c: e8 b2 ce 35 00 call 0x35cec3
11: e8 9d 57 03 0a call 0xa0357b3
16: 4d 85 ff test %r15,%r15
19: 74 ea je 0x5
1b: e8 a3 ce 35 00 call 0x35cec3
20: fb sti
21: 48 c7 44 24 40 0e 36 movq $0x45e0360e,0x40(%rsp)
28: e0 45
* 2a: 4b c7 04 2e 00 00 00 movq $0x0,(%r14,%r13,1) <-- trapping instruction
31: 00
32: 66 43 c7 44 2e 09 00 movw $0x0,0x9(%r14,%r13,1)
39: 00
3a: 43 c6 44 2e 0b 00 movb $0x0,0xb(%r14,%r13,1)
Tested on:
commit: 846bd222 Add linux-next specific files for 20250919
git tree: linux-next
console output: https://syzkaller.appspot.com/x/log.txt?x=16b15c7c580000
kernel config: https://syzkaller.appspot.com/x/.config?x=135377594f35b576
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
patch: https://syzkaller.appspot.com/x/patch.diff?x=13f2a0e2580000
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: [syzbot] [mm?] [usb?] WARNING in __alloc_skb (4)
2025-08-27 21:55 syzbot
2025-09-20 0:43 ` Hillf Danton
@ 2025-09-20 2:55 ` Hillf Danton
2025-09-20 4:48 ` syzbot
1 sibling, 1 reply; 8+ messages in thread
From: Hillf Danton @ 2025-09-20 2:55 UTC (permalink / raw)
To: syzbot; +Cc: linux-kernel, syzkaller-bugs
> 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
@@ -594,6 +594,10 @@ static void *kmalloc_reserve(unsigned in
*/
*size = (unsigned int)obj_size;
+ if (obj_size > (PAGE_SIZE << MAX_PAGE_ORDER)) {
+ obj = NULL;
+ goto out;
+ }
/*
* Try a regular allocation, when that fails and we're not entitled
* to the reserves, fail.
@@ -657,7 +661,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);
--
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: [syzbot] [mm?] [usb?] WARNING in __alloc_skb (4)
2025-09-20 2:55 ` Hillf Danton
@ 2025-09-20 4:48 ` syzbot
0 siblings, 0 replies; 8+ messages in thread
From: syzbot @ 2025-09-20 4:48 UTC (permalink / raw)
To: hdanton, linux-kernel, syzkaller-bugs
Hello,
syzbot has tested the proposed patch and the reproducer did not trigger any issue:
Reported-by: syzbot+5a2250fd91b28106c37b@syzkaller.appspotmail.com
Tested-by: syzbot+5a2250fd91b28106c37b@syzkaller.appspotmail.com
Tested on:
commit: 846bd222 Add linux-next specific files for 20250919
git tree: linux-next
console output: https://syzkaller.appspot.com/x/log.txt?x=162b5c7c580000
kernel config: https://syzkaller.appspot.com/x/.config?x=135377594f35b576
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
patch: https://syzkaller.appspot.com/x/patch.diff?x=16eabe42580000
Note: testing is done by a robot and is best-effort only.
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: [syzbot] [mm?] [usb?] WARNING in __alloc_skb (4)
[not found] <CAL4kbRMa8snwYuwi4zNjx9bNbrRg=MN+xkadQ=89Dc6URRCOog@mail.gmail.com>
@ 2025-09-20 11:37 ` syzbot
0 siblings, 0 replies; 8+ messages in thread
From: syzbot @ 2025-09-20 11:37 UTC (permalink / raw)
To: kriish.sharma2006, linux-kernel, syzkaller-bugs
Hello,
syzbot has tested the proposed patch and the reproducer did not trigger any issue:
Reported-by: syzbot+5a2250fd91b28106c37b@syzkaller.appspotmail.com
Tested-by: syzbot+5a2250fd91b28106c37b@syzkaller.appspotmail.com
Tested on:
commit: 846bd222 Add linux-next specific files for 20250919
git tree: linux-next
console output: https://syzkaller.appspot.com/x/log.txt?x=153a9858580000
kernel config: https://syzkaller.appspot.com/x/.config?x=135377594f35b576
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
patch: https://syzkaller.appspot.com/x/patch.diff?x=1132dc7c580000
Note: testing is done by a robot and is best-effort only.
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: [syzbot] [mm?] [usb?] WARNING in __alloc_skb (4)
[not found] <CAL4kbRPcgyZtXEGuiAR+dpiqfsawnwyKovtKy_vWEgowF+HDMQ@mail.gmail.com>
@ 2025-09-20 20:09 ` syzbot
0 siblings, 0 replies; 8+ messages in thread
From: syzbot @ 2025-09-20 20:09 UTC (permalink / raw)
To: kriish.sharma2006, linux-kernel, syzkaller-bugs
Hello,
syzbot has tested the proposed patch but the reproducer is still triggering an issue:
WARNING in __alloc_skb
------------[ cut here ]------------
kmalloc_reserve: request size 4294965248 exceeds KMALLOC_MAX_SIZE (4194304)
WARNING: net/core/skbuff.c:598 at kmalloc_reserve+0x2df/0x2f0 net/core/skbuff.c:596, CPU#1: dhcpcd/5527
Modules linked in:
CPU: 1 UID: 0 PID: 5527 Comm: dhcpcd Not tainted syzkaller #0 PREEMPT(full)
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 08/18/2025
RIP: 0010:kmalloc_reserve+0x2df/0x2f0 net/core/skbuff.c:596
Code: ff e8 b5 75 54 f8 c6 05 18 35 63 06 01 90 b9 00 00 40 00 48 c7 c7 60 2e b4 8c 48 c7 c6 d4 5d c3 8d 4c 89 ea e8 22 e7 17 f8 90 <0f> 0b 90 90 45 31 e4 e9 37 ff ff ff 0f 1f 44 00 00 90 90 90 90 90
RSP: 0018:ffffc90000a089b0 EFLAGS: 00010246
RAX: 40535143de383200 RBX: dffffc0000000001 RCX: ffff88802f97bc80
RDX: 0000000000000100 RSI: 0000000000000000 RDI: 0000000000000002
RBP: ffffc90000a089fc R08: ffff8880b8724293 R09: 1ffff110170e4852
R10: dffffc0000000000 R11: ffffed10170e4853 R12: 00000000fffff6c0
R13: 00000000fffff800 R14: 0000000000020820 R15: 1ffff9200014113f
FS: 00007fc29b83c740(0000) GS:ffff8881258a2000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007ffc1fdb0168 CR3: 0000000033cd0000 CR4: 00000000003526f0
Call Trace:
<IRQ>
__alloc_skb+0x142/0x2d0 net/core/skbuff.c:677
__netdev_alloc_skb+0x108/0x970 net/core/skbuff.c:741
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:3263 [inline]
process_scheduled_works+0xae1/0x17b0 kernel/workqueue.c:3346
bh_worker+0x2b1/0x600 kernel/workqueue.c:3607
tasklet_action+0xc/0x70 kernel/softirq.c:952
handle_softirqs+0x286/0x870 kernel/softirq.c:622
do_softirq+0xec/0x180 kernel/softirq.c:523
</IRQ>
<TASK>
__local_bh_enable_ip+0x17d/0x1c0 kernel/softirq.c:450
__dev_open+0x694/0x880 net/core/dev.c:1690
__dev_change_flags+0x1ea/0x6d0 net/core/dev.c:9630
netif_change_flags+0x88/0x1a0 net/core/dev.c:9693
dev_change_flags+0x130/0x260 net/core/dev_api.c:68
devinet_ioctl+0xbb4/0x1b50 net/ipv4/devinet.c:1199
inet_ioctl+0x3c0/0x4c0 net/ipv4/af_inet.c:1003
sock_do_ioctl+0xdc/0x300 net/socket.c:1241
sock_ioctl+0x576/0x790 net/socket.c:1362
vfs_ioctl fs/ioctl.c:51 [inline]
__do_sys_ioctl fs/ioctl.c:597 [inline]
__se_sys_ioctl+0xfc/0x170 fs/ioctl.c:583
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:0x7fc29b93c378
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:00007ffd8c8eaa48 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
RAX: ffffffffffffffda RBX: 0000000000000016 RCX: 00007fc29b93c378
RDX: 00007ffd8c8fac40 RSI: 0000000000008914 RDI: 0000000000000016
RBP: 0000000000000000 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 00007ffd8c90ade0
R13: 00007fc29b83c6c8 R14: 0000000000000028 R15: 0000000000008914
</TASK>
Tested on:
commit: 846bd222 Add linux-next specific files for 20250919
git tree: linux-next
console output: https://syzkaller.appspot.com/x/log.txt?x=16561534580000
kernel config: https://syzkaller.appspot.com/x/.config?x=135377594f35b576
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
patch: https://syzkaller.appspot.com/x/patch.diff?x=144b60e2580000
^ permalink raw reply [flat|nested] 8+ messages in thread
end of thread, other threads:[~2025-09-20 20:09 UTC | newest]
Thread overview: 8+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
[not found] <CAL4kbRMa8snwYuwi4zNjx9bNbrRg=MN+xkadQ=89Dc6URRCOog@mail.gmail.com>
2025-09-20 11:37 ` [syzbot] [mm?] [usb?] WARNING in __alloc_skb (4) syzbot
[not found] <CAL4kbRPcgyZtXEGuiAR+dpiqfsawnwyKovtKy_vWEgowF+HDMQ@mail.gmail.com>
2025-09-20 20:09 ` syzbot
[not found] <CAL4kbRPgrQO_QYOGBFGoPEG9OZet-LVSvGDT2+37-uiKRWh0ng@mail.gmail.com>
2025-09-19 17:28 ` 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
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox