BUG: soft lockup in net_rx_action (2)

7 vues
Accéder directement au premier message non lu

syzbot

non lue,
6 oct. 2022, 16:26:3906/10/2022
à 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=11dd3284880000
kernel config: https://syzkaller.appspot.com/x/.config?x=9b9277b418617afe
dashboard link: https://syzkaller.appspot.com/bug?extid=d22ba7b1cbf9ee86d67b
compiler: gcc version 10.2.1 20210110 (Debian 10.2.1-6)

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/98c0bdb4abb3/disk-3f8a27f9.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/ea228ff02669/vmlinux-3f8a27f9.xz

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

Bluetooth: hci1: command 0x040f tx timeout
Bluetooth: hci1: command 0x0419 tx timeout
Bluetooth: hci0: command 0x0406 tx timeout
ieee802154 phy0 wpan0: encryption failed: -22
ieee802154 phy1 wpan1: encryption failed: -22
watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [syz-executor.3:3661]
Modules linked in:
irq event stamp: 3697543
hardirqs last enabled at (3697542): [<ffffffff81982899>] kmem_cache_free+0x109/0x260 mm/slab.c:3766
hardirqs last disabled at (3697543): [<ffffffff81003d00>] trace_hardirqs_off_thunk+0x1a/0x1c
softirqs last enabled at (3685016): [<ffffffff88400678>] __do_softirq+0x678/0x980 kernel/softirq.c:318
softirqs last disabled at (3685019): [<ffffffff813927d5>] invoke_softirq kernel/softirq.c:372 [inline]
softirqs last disabled at (3685019): [<ffffffff813927d5>] irq_exit+0x215/0x260 kernel/softirq.c:412
CPU: 0 PID: 3661 Comm: syz-executor.3 Not tainted 4.19.211-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 09/22/2022
RIP: 0010:__write_once_size include/linux/compiler.h:290 [inline]
RIP: 0010:__skb_unlink include/linux/skbuff.h:1919 [inline]
RIP: 0010:__skb_dequeue include/linux/skbuff.h:1936 [inline]
RIP: 0010:process_backlog+0x1b4/0x700 net/core/dev.c:5847
Code: 0f 85 26 04 00 00 48 8d 7a 08 4c 8b 7d 08 48 c7 45 00 00 00 00 00 48 89 f9 48 c7 45 08 00 00 00 00 48 c1 e9 03 42 80 3c 21 00 <0f> 85 de 03 00 00 4c 89 f9 4c 89 7a 08 48 c1 e9 03 42 80 3c 21 00
RSP: 0018:ffff8880ba007db8 EFLAGS: 00000246 ORIG_RAX: ffffffffffffff13
RAX: 1ffff11012ac7cb9 RBX: ffff8880ba02c4c8 RCX: 1ffff11008514999
RDX: ffff8880428a4cc0 RSI: ffffffff86772c36 RDI: ffff8880428a4cc8
RBP: ffff88809563e5c0 R08: 0000000000000000 R09: 0000000000000011
R10: 0000000000000004 R11: 0000000000000000 R12: dffffc0000000000
R13: 0000000000000011 R14: 0000000000000040 R15: ffff8880ba02c310
FS: 00007fc375576700(0000) GS:ffff8880ba000000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f0cbef5f800 CR3: 00000000a1bdd000 CR4: 00000000003406f0
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:compound_head include/linux/page-flags.h:144 [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+0x1254/0x2c50 mm/memory.c:1534
Code: 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 c0 00 00 00 83 e3 01 48 89 de
RSP: 0018:ffff88803b96f770 EFLAGS: 00000246 ORIG_RAX: ffffffffffffff13
RAX: dead000000000100 RBX: 0000000000000001 RCX: ffff88803b96f9b0
RDX: 0000000000000000 RSI: ffffffff818b9e3a RDI: ffff88803b96f9c8
RBP: ffffea0002d6fb48 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000001 R11: 0000000000000000 R12: 80000000b5bed007
R13: ffffea0002d6fb40 R14: dffffc0000000000 R15: 00007fc376a83000
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:0x7fc376c025a9
Code: Bad RIP value.
RSP: 002b:00007fc375576168 EFLAGS: 00000246 ORIG_RAX: 0000000000000028
RAX: 000000000004f000 RBX: 00007fc376d23f80 RCX: 00007fc376c025a9
RDX: 0000000000000000 RSI: 0000000000000004 RDI: 0000000000000004
RBP: 00007fc376c5d580 R08: 0000000000000000 R09: 0000000000000000
R10: 00000000dffffffe R11: 0000000000000246 R12: 0000000000000000
R13: 00007ffd135ecb8f R14: 00007fc375576300 R15: 0000000000022000
Sending NMI from CPU 0 to CPUs 1:
NMI backtrace for cpu 1 skipped: idling at native_safe_halt+0xe/0x10 arch/x86/include/asm/irqflags.h:60


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

non lue,
3 févr. 2023, 15:26:3503/02/2023
à syzkaller...@googlegroups.com
Auto-closing this bug as obsolete.
Crashes did not happen for a while, no reproducer and no activity.
Répondre à tous
Répondre à l'auteur
Transférer
0 nouveau message