* [syzbot] [net?] WARNING in gro_cell_poll
@ 2026-09-18 16:57 syzbot
0 siblings, 0 replies; only message in thread
From: syzbot @ 2026-09-18 16:57 UTC (permalink / raw)
To: davem, edumazet, horms, kuba, linux-kernel, netdev, pabeni,
syzkaller-bugs
Hello,
syzbot found the following issue on:
HEAD commit: 08df884136f1 Merge tag 'thermal-7.3-rc3' of git://git.kern..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=13b88905580000
kernel config: https://syzkaller.appspot.com/x/.config?x=19560cab9a915237
dashboard link: https://syzkaller.appspot.com/bug?extid=f0661448aa9511ce744a
compiler: gcc (Debian 14.2.0-19) 14.2.0, GNU ld (GNU Binutils for Debian) 2.44
Unfortunately, I don't have any reproducer for this issue yet.
Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/607f53d96d3b/disk-08df8841.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/af77b44e9d7f/vmlinux-08df8841.xz
kernel image: https://storage.googleapis.com/syzbot-assets/ebeacfa9027e/bzImage-08df8841.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+f0661448aa9511ce744a@syzkaller.appspotmail.com
------------[ cut here ]------------
DEBUG_LOCKS_WARN_ON(l->owner)
WARNING: ./include/linux/local_lock_internal.h:47 at local_lock_acquire include/linux/local_lock_internal.h:47 [inline], CPU#1: napi/gre0-0/11827
WARNING: ./include/linux/local_lock_internal.h:47 at gro_cell_poll+0x5aa/0x6c0 net/core/gro_cells.c:66, CPU#1: napi/gre0-0/11827
Modules linked in:
CPU: 1 UID: 0 PID: 11827 Comm: napi/gre0-0 Tainted: G L syzkaller #0 PREEMPT(full)
Tainted: [L]=SOFTLOCKUP
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 08/05/2026
RIP: 0010:local_lock_acquire include/linux/local_lock_internal.h:47 [inline]
RIP: 0010:gro_cell_poll+0x5b1/0x6c0 net/core/gro_cells.c:66
Code: 8d 3d f3 aa 9a 07 48 c7 c6 40 c7 3c 8d 67 48 0f b9 3a e9 59 fe ff ff e8 dd 5e 52 f8 48 8d 3d e6 aa 9a 07 48 c7 c6 00 c7 3c 8d <67> 48 0f b9 3a eb be 31 db e9 88 fd ff ff 48 8b 7c 24 20 e8 97 a2
RSP: 0018:ffffc900033c7b70 EFLAGS: 00010293
RAX: 0000000000000000 RBX: 0000000000000000 RCX: 0000000000000200
RDX: ffff8880284e0000 RSI: ffffffff8d3cc700 RDI: ffffffff91544100
RBP: ffffe8ffffc37198 R08: 0000000000000005 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000000 R12: dffffc0000000000
R13: ffffffff9b99e5c0 R14: 0000000000000000 R15: 0000000000000000
FS: 0000000000000000(0000) GS:ffff888123c59000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000001b32617ff8 CR3: 000000005d244000 CR4: 0000000000350ef0
Call Trace:
<TASK>
__napi_poll.constprop.0+0xaf/0x450 net/core/dev.c:7787
napi_threaded_poll_loop+0x52f/0x870 net/core/dev.c:7907
napi_threaded_poll+0x3a8/0x4b0 net/core/dev.c:7962
kthread+0x373/0x450 kernel/kthread.c:436
ret_from_fork+0x730/0xd60 arch/x86/kernel/process.c:158
ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:245
</TASK>
----------------
Code disassembly (best guess):
0: 8d 3d f3 aa 9a 07 lea 0x79aaaf3(%rip),%edi # 0x79aaaf9
6: 48 c7 c6 40 c7 3c 8d mov $0xffffffff8d3cc740,%rsi
d: 67 48 0f b9 3a ud1 (%edx),%rdi
12: e9 59 fe ff ff jmp 0xfffffe70
17: e8 dd 5e 52 f8 call 0xf8525ef9
1c: 48 8d 3d e6 aa 9a 07 lea 0x79aaae6(%rip),%rdi # 0x79aab09
23: 48 c7 c6 00 c7 3c 8d mov $0xffffffff8d3cc700,%rsi
* 2a: 67 48 0f b9 3a ud1 (%edx),%rdi <-- trapping instruction
2f: eb be jmp 0xffffffef
31: 31 db xor %ebx,%ebx
33: e9 88 fd ff ff jmp 0xfffffdc0
38: 48 8b 7c 24 20 mov 0x20(%rsp),%rdi
3d: e8 .byte 0xe8
3e: 97 xchg %eax,%edi
3f: a2 .byte 0xa2
---
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 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] only message in thread
only message in thread, other threads:[~2026-09-18 16:57 UTC | newest]
Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2026-09-18 16:57 [syzbot] [net?] WARNING in gro_cell_poll syzbot
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®