BUG: soft lockup in tipc_disc_timeout (2)

4 views
Skip to first unread message

syzbot

unread,
Oct 8, 2022, 9:50:37 PM10/8/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=10f13f14880000
kernel config: https://syzkaller.appspot.com/x/.config?x=9b9277b418617afe
dashboard link: https://syzkaller.appspot.com/bug?extid=e88013e1dbd42210cd02
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+e88013...@syzkaller.appspotmail.com

audit: type=1804 audit(1665280156.971:2062): pid=11886 uid=0 auid=4294967295 ses=4294967295 subj==unconfined op=invalid_pcr cause=open_writers comm="syz-executor.5" name="/root/syzkaller-testdir37379716/syzkaller.TDn1S4/685/bus" dev="sda1" ino=14434 res=1
watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [syz-executor.0:11995]
Modules linked in:
irq event stamp: 3838147
hardirqs last enabled at (3838146): [<ffffffff81003ce4>] trace_hardirqs_on_thunk+0x1a/0x1c
hardirqs last disabled at (3838147): [<ffffffff81003d00>] trace_hardirqs_off_thunk+0x1a/0x1c
softirqs last enabled at (3822342): [<ffffffff88400678>] __do_softirq+0x678/0x980 kernel/softirq.c:318
softirqs last disabled at (3822345): [<ffffffff813927d5>] invoke_softirq kernel/softirq.c:372 [inline]
softirqs last disabled at (3822345): [<ffffffff813927d5>] irq_exit+0x215/0x260 kernel/softirq.c:412
CPU: 0 PID: 11995 Comm: syz-executor.0 Not tainted 4.19.211-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 09/22/2022
RIP: 0010:find_rr_leaf net/ipv6/route.c:714 [inline]
RIP: 0010:rt6_select net/ipv6/route.c:769 [inline]
RIP: 0010:fib6_table_lookup+0x451/0xf40 net/ipv6/route.c:1876
Code: e8 84 1d 5a fa 48 8d bb 98 00 00 00 48 89 f8 48 c1 e8 03 42 0f b6 04 38 84 c0 74 08 3c 03 0f 8e 78 09 00 00 8b ab 98 00 00 00 <44> 89 ef 89 ee e8 45 1e 5a fa 41 39 ed 0f 85 02 01 00 00 e8 47 1d
RSP: 0018:ffff8880ba007488 EFLAGS: 00000246 ORIG_RAX: ffffffffffffff13
RAX: 0000000000000000 RBX: ffff88809ca89140 RCX: ffffffff870867de
RDX: 0000000000000100 RSI: ffffffff870867ec RDI: ffff88809ca891d8
RBP: 0000000000000100 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000007 R11: ffffffff870256e0 R12: 0000000000000000
R13: 0000000000000100 R14: 0000000000003f49 R15: dffffc0000000000
FS: 00007f0da94a6700(0000) GS:ffff8880ba000000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00005555557e5848 CR3: 000000001b2f3000 CR4: 00000000003406f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<IRQ>
ip6_pol_route+0x180/0x1270 net/ipv6/route.c:1909
fib6_rule_lookup+0x22d/0x4e0 net/ipv6/fib6_rules.c:122
ip6_route_output_flags+0x2b0/0x350 net/ipv6/route.c:2163
ip6_dst_lookup_tail+0x566/0x19b0 net/ipv6/ip6_output.c:1019
ip6_dst_lookup_flow+0x8c/0x1d0 net/ipv6/ip6_output.c:1120
tipc_udp_xmit+0x2c4/0xc10 net/tipc/udp_media.c:192
tipc_udp_send_msg+0x279/0x490 net/tipc/udp_media.c:248
tipc_bearer_xmit_skb+0x15b/0x330 net/tipc/bearer.c:518
tipc_disc_timeout+0x855/0xc90 net/tipc/discover.c:332
call_timer_fn+0x177/0x700 kernel/time/timer.c:1338
expire_timers+0x243/0x4e0 kernel/time/timer.c:1375
__run_timers kernel/time/timer.c:1696 [inline]
run_timer_softirq+0x21c/0x670 kernel/time/timer.c:1709
__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:lock_page_memcg+0x75/0x220 mm/memcontrol.c:1921
Code: 00 00 0f 1f 44 00 00 4c 8d 7b 38 48 b8 00 00 00 00 00 fc ff df 4c 89 fa 48 c1 ea 03 80 3c 02 00 0f 85 78 01 00 00 4c 8b 63 38 <4d> 89 fd 49 be 00 00 00 00 00 fc ff df 49 c1 ed 03 4d 01 f5 4d 85
RSP: 0018:ffff8880253af6c0 EFLAGS: 00000246 ORIG_RAX: ffffffffffffff13
RAX: dffffc0000000000 RBX: ffffea00028b9280 RCX: ffffffff81518c83
RDX: 1ffffd4000517257 RSI: 0000000000000004 RDI: ffff8880ba022ad0
RBP: ffffea00028b9280 R08: 0000000000000000 R09: ffffed101740455a
R10: ffff8880ba022ad3 R11: 0000000000000000 R12: 0000000000000000
R13: 0000000000000000 R14: ffffea00028b9280 R15: ffffea00028b92b8
page_remove_file_rmap+0x36/0xa30 mm/rmap.c:1212
page_remove_rmap+0xe5/0x120 mm/rmap.c:1297
zap_pte_range mm/memory.c:1350 [inline]
zap_pmd_range mm/memory.c:1463 [inline]
zap_pud_range mm/memory.c:1492 [inline]
zap_p4d_range mm/memory.c:1513 [inline]
unmap_page_range+0x147d/0x2c50 mm/memory.c:1534
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:0x7f0daab325a9
Code: Bad RIP value.
RSP: 002b:00007f0da94a6168 EFLAGS: 00000246 ORIG_RAX: 0000000000000055
RAX: 0000000000000005 RBX: 00007f0daac53f80 RCX: 00007f0daab325a9
RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000020000040
RBP: 00007f0daab8d580 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007fffdfb2129f R14: 00007f0da94a6300 R15: 0000000000022000
Sending NMI from CPU 0 to CPUs 1:
NMI backtrace for cpu 1
CPU: 1 PID: 11939 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:batadv_hardif_get_by_netdev+0x14b/0x3e0 net/batman-adv/hard-interface.c:83
Code: 0f 85 7b 02 00 00 4d 8b 3f 49 81 ff 60 8c db 8d 0f 84 af 01 00 00 e8 34 b9 8a f9 49 8d 7f 20 48 89 f8 48 c1 e8 03 80 3c 18 00 <0f> 85 5e 02 00 00 49 39 6f 20 75 ba e8 14 b9 8a f9 4d 8d 6f 30 be
RSP: 0018:ffff88801aa0eb90 EFLAGS: 00000246
RAX: 1ffff1101376764c RBX: dffffc0000000000 RCX: ffffc90008641000
RDX: 0000000000040000 RSI: ffffffff87d7cc3c RDI: ffff88809bb3b260
RBP: ffff888044e20780 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000001 R11: 0000000000000000 R12: ffff888044e20780
R13: 0000000000000000 R14: 0000000000000000 R15: ffff88809bb3b240
FS: 00007f1c99b23700(0000) GS:ffff8880ba100000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000555556b67708 CR3: 000000001b2f3000 CR4: 00000000003406e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
batadv_hard_if_event+0xaf/0x15c0 net/batman-adv/hard-interface.c:1035
notifier_call_chain+0xc0/0x230 kernel/notifier.c:93
call_netdevice_notifiers net/core/dev.c:1762 [inline]
__dev_open+0x104/0x3a0 net/core/dev.c:1391
dev_open net/core/dev.c:1437 [inline]
dev_open+0xde/0x140 net/core/dev.c:1430
bond_enslave+0x958/0x5250 drivers/net/bonding/bond_main.c:1561
do_set_master+0x1c8/0x220 net/core/rtnetlink.c:2321
rtnl_newlink+0x1279/0x15c0 net/core/rtnetlink.c:3170
rtnetlink_rcv_msg+0x453/0xb80 net/core/rtnetlink.c:4782
netlink_rcv_skb+0x160/0x440 net/netlink/af_netlink.c:2463
netlink_unicast_kernel net/netlink/af_netlink.c:1325 [inline]
netlink_unicast+0x4d5/0x690 net/netlink/af_netlink.c:1351
netlink_sendmsg+0x6c3/0xc50 net/netlink/af_netlink.c:1917
sock_sendmsg_nosec net/socket.c:651 [inline]
sock_sendmsg+0xc3/0x120 net/socket.c:661
___sys_sendmsg+0x7bb/0x8e0 net/socket.c:2227
__sys_sendmsg net/socket.c:2265 [inline]
__do_sys_sendmsg net/socket.c:2274 [inline]
__se_sys_sendmsg net/socket.c:2272 [inline]
__x64_sys_sendmsg+0x132/0x220 net/socket.c:2272
do_syscall_64+0xf9/0x620 arch/x86/entry/common.c:293
entry_SYSCALL_64_after_hwframe+0x49/0xbe
RIP: 0033:0x7f1c9b1f15a9
Code: ff ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 b8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007f1c99b23168 EFLAGS: 00000246 ORIG_RAX: 000000000000002e
RAX: ffffffffffffffda RBX: 00007f1c9b313120 RCX: 00007f1c9b1f15a9
RDX: 0000000000000000 RSI: 0000000020000040 RDI: 0000000000000005
RBP: 00007f1c9b24c580 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007ffd443defff R14: 00007f1c99b23300 R15: 0000000000022000


---
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,
Feb 5, 2023, 8:50:33 PM2/5/23
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