From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mail-io1-f70.google.com (mail-io1-f70.google.com [209.85.166.70]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id DB4671369B0 for ; Thu, 4 Jul 2024 19:37:53 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=209.85.166.70 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1720121875; cv=none; b=SCozZqpRG3XHQepMiLUwCSCzgRZvVFx168hj1E0S86sOar0Z+pVtcCzSWLbep2mbaWaAgUFPUWxBuja4FvzclFCfVEePPEzYw16ZpIKMj90HyeBXW1Aym5ZiczC7vmbl73X23jA3Qk3VdSSjVXe35qypOkz9eUqH+D9sxpUWTgE= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1720121875; c=relaxed/simple; bh=YO71hz8bX8jhJqoenPdrwp6IllvL7Gis479uJ23wM/g=; h=MIME-Version:Date:In-Reply-To:Message-ID:Subject:From:To: Content-Type; b=h8Owri/hXwdzjqawCQjGFwbuUnzV0faKKVjpPUXVlxF9yQDeYPYzGsLSofgAjet/NKlPx9UInvxfoGxmRmXqQNZWehiUgyvQLkbi3/FX50Zen9wQfHXGcURW4IDOUbRRfKhZmS2DLAAuMcCk8bny39nGvi81oGuZHm1XD6z7gZc= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=fail (p=none dis=none) header.from=syzkaller.appspotmail.com; spf=pass smtp.mailfrom=M3KW2WVRGUFZ5GODRSRYTGD7.apphosting.bounces.google.com; arc=none smtp.client-ip=209.85.166.70 Authentication-Results: smtp.subspace.kernel.org; dmarc=fail (p=none dis=none) header.from=syzkaller.appspotmail.com Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=M3KW2WVRGUFZ5GODRSRYTGD7.apphosting.bounces.google.com Received: by mail-io1-f70.google.com with SMTP id ca18e2360f4ac-7f639551768so122416639f.3 for ; Thu, 04 Jul 2024 12:37:53 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1720121873; x=1720726673; h=to:from:subject:message-id:in-reply-to:date:mime-version :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=YV748nmFlmNgH955MNu0lEryGP1Z/LgQ2Rjw28RmVb8=; b=fEoYH0sK/9KuDOH771LrZizpYs8k1ZdLAVxJr2vuX2Z0lcSUIH8Ta4pCRT+Lk5nbPH AY6t1JYweWW7yV3lzNcmmY/2JjB2Mhh7qXxX31dJTKZ9BKAQhL5GG2Q6Zfc2zE2aE2Yd WTZJCipv8qbyAjZ3OlY0jRiGPYbmHfQSISGzQ7Xh8C1qNO7AIa1PnLG58OMPbiS2kh39 xXgH2rC+Xk+vi4YQNA8jYK3bQV2raWXHOCEBqExxoGSCa+dAa7QQqKJ+RB6YUt/Qh8T5 K+2U9Yb8BZt9kilYWTF5BpA82ZOJOki6dCyJchOpfv3JBXuLs8ROiD5aP6noIUJYoHQ9 yQqA== X-Gm-Message-State: AOJu0YxXF+dbLY8MEEs8zKf3ibJcBbrE+JfykwpZ7ldruUn2d3YYIFVI Glyl5vPIT7HPXTpATqnc3qObcD2jTbaGmTm4z1VilFvcs/7Y9vMKNFRI07MUvtE7t596xG3l9Uz PM/0C12EQh72r0gwBamutY36Yu/GvEPZVGbGgGe817PqT6Oy1Xa+sskw= X-Google-Smtp-Source: AGHT+IHfX7tbO5xrA69oI1dPxpQB75YMWVQZcrSAs8clRgQJscmEZ0XedVnfUxmrc7oND1GQQgehnLPegVZI2iXDXTCxcrjyg/9X Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 X-Received: by 2002:a05:6602:6282:b0:7f3:d924:8618 with SMTP id ca18e2360f4ac-7f66db5e367mr13076939f.0.1720121873028; Thu, 04 Jul 2024 12:37:53 -0700 (PDT) Date: Thu, 04 Jul 2024 12:37:53 -0700 In-Reply-To: <00000000000045f576061c6e8142@google.com> X-Google-Appengine-App-Id: s~syzkaller X-Google-Appengine-App-Id-Alias: syzkaller Message-ID: <0000000000003666c4061c711582@google.com> Subject: Re: [syzbot] Re: [syzbot] [batman?] INFO: rcu detected stall in batadv_iv_send_outstanding_bat_ogm_packet (5) From: syzbot To: linux-kernel@vger.kernel.org Content-Type: text/plain; charset="UTF-8" For archival purposes, forwarding an incoming command email to linux-kernel@vger.kernel.org. *** Subject: Re: [syzbot] [batman?] INFO: rcu detected stall in batadv_iv_send_outstanding_bat_ogm_packet (5) Author: sven@narfation.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@syzkaller.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): [] __exit_to_kernel_mode arch/arm64/kernel/entry-common.c:85 [inline] > hardirqs last enabled at (132862): [] exit_to_kernel_mode+0xdc/0x10c arch/arm64/kernel/entry-common.c:95 > hardirqs last disabled at (132863): [] __el1_irq arch/arm64/kernel/entry-common.c:533 [inline] > hardirqs last disabled at (132863): [] el1_interrupt+0x24/0x68 arch/arm64/kernel/entry-common.c:551 > softirqs last enabled at (128034): [] softirq_handle_end kernel/softirq.c:399 [inline] > softirqs last enabled at (128034): [] __do_softirq+0xac8/0xce4 kernel/softirq.c:582 > softirqs last disabled at (128036): [] spin_lock_bh include/linux/spinlock.h:356 [inline] > softirqs last disabled at (128036): [] 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@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 >