[v5.15] WARNING in __alloc_skb

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 2f693b607545 Linux 5.15.187
git tree: linux-5.15.y
console output: https://syzkaller.appspot.com/x/log.txt?x=1278918c580000
kernel config: https://syzkaller.appspot.com/x/.config?x=c91c2d91ea1a4388
dashboard link: https://syzkaller.appspot.com/bug?extid=bf12cb89f95bee8e5efd
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=1678918c580000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/7769e50dbae7/disk-2f693b60.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/ca8639ca4ec3/vmlinux-2f693b60.xz
kernel image: https://storage.googleapis.com/syzbot-assets/34e626fbb90f/bzImage-2f693b60.xz
mounted in repro: https://storage.googleapis.com/syzbot-assets/277c6762eb94/mount_3.gz
fsck result: failed (log: https://syzkaller.appspot.com/x/fsck.log?x=15bdbd82580000)

IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+bf12cb...@syzkaller.appspotmail.com

------------[ cut here ]------------
WARNING: CPU: 1 PID: 20 at mm/page_alloc.c:5449 current_gfp_context include/linux/sched/mm.h:-1 [inline]
WARNING: CPU: 1 PID: 20 at mm/page_alloc.c:5449 __alloc_pages+0x391/0x470 mm/page_alloc.c:5461
Modules linked in:
CPU: 1 PID: 20 Comm: ksoftirqd/1 Not tainted 5.15.187-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 05/07/2025
RIP: 0010:__alloc_pages+0x391/0x470 mm/page_alloc.c:5449
Code: 31 ff e9 b2 fe ff ff e8 bd fd f5 07 44 89 e1 80 e1 07 80 c1 03 38 c1 0f 8c 50 fd ff ff 4c 89 e7 e8 44 ac 09 00 e9 43 fd ff ff <0f> 0b 45 31 ff e9 ef fe ff ff 65 44 8b 2d 75 75 4e 7e 41 83 fd 08
RSP: 0018:ffffc90000da77c0 EFLAGS: 00010246
RAX: ffffc90000da7800 RBX: 1ffff920001b4efc RCX: 0000000000000000
RDX: 0000000000000028 RSI: 0000000000000000 RDI: ffffc90000da7828
RBP: ffffc90000da78a8 R08: dffffc0000000000 R09: ffffc90000da7800
R10: fffff520001b4f05 R11: 1ffff920001b4f00 R12: dffffc0000000000
R13: 0000000000000000 R14: 0000000000060a20 R15: 0000000000000014
FS: 0000000000000000(0000) GS:ffff8880b9100000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000561a89084138 CR3: 000000001f93a000 CR4: 00000000003506e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
__alloc_pages_node include/linux/gfp.h:570 [inline]
alloc_pages_node include/linux/gfp.h:584 [inline]
kmalloc_large_node+0x7d/0x190 mm/slub.c:4421
__kmalloc_node_track_caller+0x22e/0x3a0 mm/slub.c:4944
kmalloc_reserve net/core/skbuff.c:364 [inline]
__alloc_skb+0x25d/0x750 net/core/skbuff.c:427
__netdev_alloc_skb+0x103/0x4a0 net/core/skbuff.c:494
rx_submit+0x100/0xa50 drivers/net/usb/usbnet.c:-1
rx_alloc_submit+0xa6/0x130 drivers/net/usb/usbnet.c:1533
usbnet_bh+0x959/0xcd0 drivers/net/usb/usbnet.c:1595
tasklet_action_common+0x298/0x400 kernel/softirq.c:806
handle_softirqs+0x328/0x820 kernel/softirq.c:576
run_ksoftirqd+0x98/0xf0 kernel/softirq.c:943
smpboot_thread_fn+0x4f6/0x970 kernel/smpboot.c:164
kthread+0x436/0x520 kernel/kthread.c:334
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:287
</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 syzk...@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

[syzbot]

Auto-closing this bug as obsolete.
No recent activity, existing reproducers are no longer triggering the issue.