BUG: soft lockup in net_rx_action

36 views
Skip to first unread message

syzbot

unread,
Jan 16, 2022, 7:12:19 AM1/16/22
to syzkaller...@googlegroups.com
Hello,

syzbot found the following issue on:

HEAD commit: 3f8a27f9e27b Linux 4.19.211
git tree: linux-4.19.y
console output: https://syzkaller.appspot.com/x/log.txt?x=1403585bb00000
kernel config: https://syzkaller.appspot.com/x/.config?x=9b9277b418617afe
dashboard link: https://syzkaller.appspot.com/bug?extid=b31af39c8c167c789a7b
compiler: gcc version 10.2.1 20210110 (Debian 10.2.1-6)

Unfortunately, I don't have any reproducer for this issue yet.

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

EXT4-fs (loop0): Unrecognized mount option "����" or missing value
tmpfs: Bad value '5%354m' for mount option 'nr_blocks'
ieee802154 phy0 wpan0: encryption failed: -22
ieee802154 phy1 wpan1: encryption failed: -22
watchdog: BUG: soft lockup - CPU#1 stuck for 21s! [syz-executor.3:12955]
Modules linked in:
irq event stamp: 3567637
hardirqs last enabled at (3567636): [<ffffffff86772f5e>] process_backlog+0x45e/0x700 net/core/dev.c:5875
hardirqs last disabled at (3567637): [<ffffffff81003d00>] trace_hardirqs_off_thunk+0x1a/0x1c
softirqs last enabled at (3546344): [<ffffffff88400678>] __do_softirq+0x678/0x980 kernel/softirq.c:318
softirqs last disabled at (3546347): [<ffffffff813927d5>] invoke_softirq kernel/softirq.c:372 [inline]
softirqs last disabled at (3546347): [<ffffffff813927d5>] irq_exit+0x215/0x260 kernel/softirq.c:412
CPU: 1 PID: 12955 Comm: syz-executor.3 Not tainted 4.19.211-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
RIP: 0010:process_backlog+0x48e/0x700 net/core/dev.c:5844
Code: 89 48 c1 e8 03 42 80 3c 20 00 0f 85 9c 01 00 00 48 83 3d 1c 53 7a 03 00 0f 84 e3 00 00 00 e8 e9 55 eb fa fb 66 0f 1f 44 00 00 <31> ff 89 ee e8 09 57 eb fa 40 84 ed 0f 85 5f fc ff ff e9 33 fe ff
RSP: 0018:ffff8880ba107db8 EFLAGS: 00000206 ORIG_RAX: ffffffffffffff13
RAX: ffff888035498080 RBX: ffff8880ba12c4c8 RCX: 1ffff11006a93125
RDX: 0000000000000100 RSI: ffffffff86772f87 RDI: ffff888035498904
RBP: 0000000000000001 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000000 R12: dffffc0000000000
R13: 0000000000000000 R14: 0000000000000040 R15: ffff8880ba12c490
FS: 00007f51a3714700(0000) GS:ffff8880ba100000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007fac14b95000 CR3: 0000000009e6d000 CR4: 00000000003406e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<IRQ>
napi_poll net/core/dev.c:6280 [inline]
net_rx_action+0x4ac/0xfb0 net/core/dev.c:6346
__do_softirq+0x265/0x980 kernel/softirq.c:292
invoke_softirq kernel/softirq.c:372 [inline]
irq_exit+0x215/0x260 kernel/softirq.c:412
exiting_irq arch/x86/include/asm/apic.h:536 [inline]
smp_apic_timer_interrupt+0x136/0x550 arch/x86/kernel/apic/apic.c:1098
apic_timer_interrupt+0xf/0x20 arch/x86/entry/entry_64.S:894
</IRQ>
RIP: 0010:__read_once_size include/linux/compiler.h:263 [inline]
RIP: 0010:compound_head include/linux/page-flags.h:142 [inline]
RIP: 0010:PageAnon include/linux/page-flags.h:418 [inline]
RIP: 0010:zap_pte_range mm/memory.c:1340 [inline]
RIP: 0010:zap_pmd_range mm/memory.c:1463 [inline]
RIP: 0010:zap_pud_range mm/memory.c:1492 [inline]
RIP: 0010:zap_p4d_range mm/memory.c:1513 [inline]
RIP: 0010:unmap_page_range+0x124a/0x2c50 mm/memory.c:1534
Code: 39 79 18 48 0f 43 41 18 4d 85 ed 48 89 41 18 0f 84 36 fe ff ff e8 36 e7 d6 ff 49 8d 6d 08 48 89 e8 48 c1 e8 03 42 80 3c 30 00 <0f> 85 df 16 00 00 49 8b 45 08 31 ff 4d 89 ec 48 89 c3 48 89 84 24
RSP: 0018:ffff8880325e7770 EFLAGS: 00000246 ORIG_RAX: ffffffffffffff13
RAX: 1ffffd40004e57b1 RBX: 0000000000000001 RCX: ffff8880325e79b0
RDX: 0000000000000000 RSI: ffffffff818b9e3a RDI: ffff8880325e79c8
RBP: ffffea000272bd88 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000001 R11: 0000000000000000 R12: 800000009caf6007
R13: ffffea000272bd80 R14: dffffc0000000000 R15: 00007f51a423c000
unmap_single_vma+0x198/0x300 mm/memory.c:1579
unmap_vmas+0xa9/0x180 mm/memory.c:1609
exit_mmap+0x2b9/0x530 mm/mmap.c:3093
__mmput kernel/fork.c:1016 [inline]
mmput+0x14e/0x4a0 kernel/fork.c:1037
exit_mm kernel/exit.c:549 [inline]
do_exit+0xaec/0x2be0 kernel/exit.c:857
do_group_exit+0x125/0x310 kernel/exit.c:967
get_signal+0x3f2/0x1f70 kernel/signal.c:2589
do_signal+0x8f/0x1670 arch/x86/kernel/signal.c:799
exit_to_usermode_loop+0x204/0x2a0 arch/x86/entry/common.c:163
prepare_exit_to_usermode arch/x86/entry/common.c:198 [inline]
syscall_return_slowpath arch/x86/entry/common.c:271 [inline]
do_syscall_64+0x538/0x620 arch/x86/entry/common.c:296
entry_SYSCALL_64_after_hwframe+0x49/0xbe
RIP: 0033:0x7f51a4d9efe9
Code: Bad RIP value.
RSP: 002b:00007f51a3714168 EFLAGS: 00000246 ORIG_RAX: 0000000000000028
RAX: fffffffffffffffb RBX: 00007f51a4eb1f60 RCX: 00007f51a4d9efe9
RDX: 0000000000000000 RSI: 0000000000000006 RDI: 0000000000000006
RBP: 00007f51a4df908d R08: 0000000000000000 R09: 0000000000000000
R10: 00000000ffffdffa R11: 0000000000000246 R12: 0000000000000000
R13: 00007ffd3945c6ff R14: 00007f51a3714300 R15: 0000000000022000
Sending NMI from CPU 1 to CPUs 0:
NMI backtrace for cpu 0 skipped: idling at native_safe_halt+0xe/0x10 arch/x86/include/asm/irqflags.h:60
----------------
Code disassembly (best guess):
0: 89 48 c1 mov %ecx,-0x3f(%rax)
3: e8 03 42 80 3c callq 0x3c80420b
8: 20 00 and %al,(%rax)
a: 0f 85 9c 01 00 00 jne 0x1ac
10: 48 83 3d 1c 53 7a 03 cmpq $0x0,0x37a531c(%rip) # 0x37a5334
17: 00
18: 0f 84 e3 00 00 00 je 0x101
1e: e8 e9 55 eb fa callq 0xfaeb560c
23: fb sti
24: 66 0f 1f 44 00 00 nopw 0x0(%rax,%rax,1)
* 2a: 31 ff xor %edi,%edi <-- trapping instruction
2c: 89 ee mov %ebp,%esi
2e: e8 09 57 eb fa callq 0xfaeb573c
33: 40 84 ed test %bpl,%bpl
36: 0f 85 5f fc ff ff jne 0xfffffc9b
3c: e9 .byte 0xe9
3d: 33 fe xor %esi,%edi
3f: ff .byte 0xff


---
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.

syzbot

unread,
May 16, 2022, 8:13:19 AM5/16/22
to syzkaller...@googlegroups.com
Auto-closing this bug as obsolete.
Crashes did not happen for a while, no reproducer and no activity.
Reply all
Reply to author
Forward
0 new messages