linux-kernel - [syzbot] [kernel?] WARNING in srcu_invoke

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Message-ID: <0000000000000cfa3f0617de399a@google.com>
Date: Tue, 07 May 2024 07:44:27 -0700
From: syzbot <syzbot+2250e31d8f78fffa4768@...kaller.appspotmail.com>
To: bp@...en8.de, dave.hansen@...ux.intel.com, hpa@...or.com, 
	linux-kernel@...r.kernel.org, mingo@...hat.com, 
	syzkaller-bugs@...glegroups.com, tglx@...utronix.de, x86@...nel.org
Subject: [syzbot] [kernel?] WARNING in srcu_invoke_callbacks

Hello,

syzbot found the following issue on:

HEAD commit:    f03359bca01b Merge tag 'for-6.9-rc6-tag' of git://git.kern..
git tree:       upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=16968250980000
kernel config:  https://syzkaller.appspot.com/x/.config?x=3310e643b6ef5d69
dashboard link: https://syzkaller.appspot.com/bug?extid=2250e31d8f78fffa4768
compiler:       gcc (Debian 12.2.0-14) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/1b4deeb2639b/disk-f03359bc.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/f3c3d98db8ef/vmlinux-f03359bc.xz
kernel image: https://storage.googleapis.com/syzbot-assets/6f79ee1ae20f/bzImage-f03359bc.xz

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

------------[ cut here ]------------
WARNING: CPU: 0 PID: 928 at kernel/rcu/srcutree.c:1758 srcu_invoke_callbacks+0x412/0x490 kernel/rcu/srcutree.c:1758
Modules linked in:
CPU: 0 PID: 928 Comm: kworker/0:2 Not tainted 6.9.0-rc6-syzkaller-00131-gf03359bca01b #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 03/27/2024
Workqueue: rcu_gp srcu_invoke_callbacks
RIP: 0010:srcu_invoke_callbacks+0x412/0x490 kernel/rcu/srcutree.c:1758
Code: 10 e8 82 ff 74 00 e9 b2 fd ff ff 48 8b 7c 24 10 e8 63 00 75 00 e9 2c fe ff ff 48 8b 7c 24 10 e8 54 00 75 00 e9 41 ff ff ff 90 <0f> 0b 90 e9 fc fe ff ff 4c 89 ff e8 de ff 74 00 e9 b2 fe ff ff 4c
RSP: 0018:ffffc90004847bf8 EFLAGS: 00010202
RAX: 0000000000000000 RBX: 0000000000000000 RCX: 1ffffffff27bdd6c
RDX: 1ffff92000908f87 RSI: ffffffff8b0cae00 RDI: ffffc90004847c38
RBP: ffffe8ffff804160 R08: 0000000000000001 R09: fffffbfff27bb636
R10: ffffffff93ddb1b7 R11: 0000000000000000 R12: 1ffff92000908f83
R13: dffffc0000000000 R14: ffffc90004847c38 R15: ffffc9000405f6d8
FS:  0000000000000000(0000) GS:ffff8880b9400000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000000020071000 CR3: 000000007b086000 CR4: 00000000003526f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
 <TASK>
 process_one_work+0x9a9/0x1ac0 kernel/workqueue.c:3267
 process_scheduled_works kernel/workqueue.c:3348 [inline]
 worker_thread+0x6c8/0xf70 kernel/workqueue.c:3429
 kthread+0x2c1/0x3a0 kernel/kthread.c:388
 ret_from_fork+0x45/0x80 arch/x86/kernel/process.c:147
 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:244
 </TASK>


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