Message-ID: <0000000000003666c4061c711582@google.com>
Date: Thu, 04 Jul 2024 12:37:53 -0700
From: syzbot <syzbot+7beee86dd68b7ee38e4a@...kaller.appspotmail.com>
To: linux-kernel@...r.kernel.org
Subject: Re: [syzbot] Re: [syzbot] [batman?] INFO: rcu detected stall in
 batadv_iv_send_outstanding_bat_ogm_packet (5)

For archival purposes, forwarding an incoming command email to
linux-kernel@...r.kernel.org.

***

Subject: Re: [syzbot] [batman?] INFO: rcu detected stall in batadv_iv_send_outstanding_bat_ogm_packet (5)
Author: sven@...fation.org

On Thursday, 4 July 2024 18:33:21 CEST syzbot wrote:
> Hello,
> 
> syzbot found the following issue on:
> 
> HEAD commit:    707081b61156 Merge branch 'for-next/core', remote-tracking..
> git tree:       git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci
> console output: https://syzkaller.appspot.com/x/log.txt?x=1182b083180000
> kernel config:  https://syzkaller.appspot.com/x/.config?x=caeac3f3565b057a
> dashboard link: https://syzkaller.appspot.com/bug?extid=7beee86dd68b7ee38e4a
> compiler:       Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
> userspace arch: arm64

#syz dup: [syzbot] [batman?] BUG: soft lockup in sys_sendmsg
#syz fix: batman-adv: Avoid infinite loop trying to resize local TT

> 
> Unfortunately, I don't have any reproducer for this issue yet.
> 
> Downloadable assets:
> disk image: https://storage.googleapis.com/syzbot-assets/6cad68bf7532/disk-707081b6.raw.xz
> vmlinux: https://storage.googleapis.com/syzbot-assets/1a27e5400778/vmlinux-707081b6.xz
> kernel image: https://storage.googleapis.com/syzbot-assets/67dfc53755d0/Image-707081b6.gz.xz
> 
> IMPORTANT: if you fix the issue, please add the following tag to the commit:
> Reported-by: syzbot+7beee86dd68b7ee38e4a@...kaller.appspotmail.com
> 
> watchdog: BUG: soft lockup - CPU#0 stuck for 27s! [kworker/u4:5:575]
> Modules linked in:
> irq event stamp: 132863
> hardirqs last  enabled at (132862): [<ffff80008ad68de8>] __exit_to_kernel_mode arch/arm64/kernel/entry-common.c:85 [inline]
> hardirqs last  enabled at (132862): [<ffff80008ad68de8>] exit_to_kernel_mode+0xdc/0x10c arch/arm64/kernel/entry-common.c:95
> hardirqs last disabled at (132863): [<ffff80008ad66a78>] __el1_irq arch/arm64/kernel/entry-common.c:533 [inline]
> hardirqs last disabled at (132863): [<ffff80008ad66a78>] el1_interrupt+0x24/0x68 arch/arm64/kernel/entry-common.c:551
> softirqs last  enabled at (128034): [<ffff80008002189c>] softirq_handle_end kernel/softirq.c:399 [inline]
> softirqs last  enabled at (128034): [<ffff80008002189c>] __do_softirq+0xac8/0xce4 kernel/softirq.c:582
> softirqs last disabled at (128036): [<ffff80008aad75f4>] spin_lock_bh include/linux/spinlock.h:356 [inline]
> softirqs last disabled at (128036): [<ffff80008aad75f4>] batadv_tt_local_commit_changes+0x24/0x44 net/batman-adv/translation-table.c:3717
> CPU: 0 PID: 575 Comm: kworker/u4:5 Not tainted 6.8.0-rc7-syzkaller-g707081b61156 #0
> Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 03/27/2024
> Workqueue: bat_events batadv_iv_send_outstanding_bat_ogm_packet
> pstate: 00400005 (nzcv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--)
> pc : queued_spin_lock_slowpath+0x15c/0xcf8 kernel/locking/qspinlock.c:383
> lr : queued_spin_lock_slowpath+0x168/0xcf8 kernel/locking/qspinlock.c:383
> sp : ffff800098c77720
> x29: ffff800098c777c0 x28: 1fffe0001b8a126a x27: 1ffff0001318eef0
> x26: dfff800000000000 x25: 1fffe0001b8a126c x24: ffff800098c77740
> x23: ffff800098c77780 x22: ffff70001318eee8 x21: 0000000000000001
> x20: 0000000000000001 x19: ffff0000dc509350 x18: ffff0001b4015840
> x17: ffff800125414000 x16: ffff8000809fd934 x15: 0000000000000001
> x14: 1fffe0001b8a126a x13: 0000000000000000 x12: 0000000000000000
> x11: ffff60001b8a126b x10: 1fffe0001b8a126a x9 : 0000000000000000
> x8 : 0000000000000001 x7 : ffff80008aad75f4 x6 : 0000000000000000
> x5 : 0000000000000000 x4 : 0000000000000001 x3 : ffff80008ae5db50
> x2 : 0000000000000000 x1 : 0000000000000001 x0 : 0000000000000001
> Call trace:
>  __cmpwait_case_8 arch/arm64/include/asm/cmpxchg.h:229 [inline]
>  __cmpwait arch/arm64/include/asm/cmpxchg.h:257 [inline]
>  queued_spin_lock_slowpath+0x15c/0xcf8 kernel/locking/qspinlock.c:383
>  queued_spin_lock include/asm-generic/qspinlock.h:114 [inline]
>  do_raw_spin_lock+0x320/0x348 kernel/locking/spinlock_debug.c:116
>  __raw_spin_lock_bh include/linux/spinlock_api_smp.h:127 [inline]
>  _raw_spin_lock_bh+0x50/0x60 kernel/locking/spinlock.c:178
>  spin_lock_bh include/linux/spinlock.h:356 [inline]
>  batadv_tt_local_commit_changes+0x24/0x44 net/batman-adv/translation-table.c:3717
>  batadv_iv_ogm_schedule_buff net/batman-adv/bat_iv_ogm.c:811 [inline]
>  batadv_iv_ogm_schedule+0x1ec/0xdf0 net/batman-adv/bat_iv_ogm.c:868
>  batadv_iv_send_outstanding_bat_ogm_packet+0x740/0x900 net/batman-adv/bat_iv_ogm.c:1712
>  process_one_work+0x694/0x1204 kernel/workqueue.c:2633
>  process_scheduled_works kernel/workqueue.c:2706 [inline]
>  worker_thread+0x938/0xef4 kernel/workqueue.c:2787
>  kthread+0x288/0x310 kernel/kthread.c:388
>  ret_from_fork+0x10/0x20 arch/arm64/kernel/entry.S:860
> 
> 
> ---
> 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@...glegroups.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
> 

Powered by blists - more mailing lists