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

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: <66f71696.050a0220.38ace9.0031.GAE@google.com>
Date: Fri, 27 Sep 2024 13:33:26 -0700
From: syzbot <syzbot+5769bce04b3a8294deda@...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 try_check_zero (2)

Hello,

syzbot found the following issue on:

HEAD commit:    40e0c9d414f5 Add linux-next specific files for 20240927
git tree:       linux-next
console output: https://syzkaller.appspot.com/x/log.txt?x=14b186a9980000
kernel config:  https://syzkaller.appspot.com/x/.config?x=a311a9ffbda5a19f
dashboard link: https://syzkaller.appspot.com/bug?extid=5769bce04b3a8294deda
compiler:       Debian clang version 15.0.6, 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/ea0d6ab93926/disk-40e0c9d4.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/27d031093999/vmlinux-40e0c9d4.xz
kernel image: https://storage.googleapis.com/syzbot-assets/f406836af354/bzImage-40e0c9d4.xz

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

------------[ cut here ]------------
Mixed NMI-safe readers for srcu_struct at 0xffffc900037148b8.
WARNING: CPU: 1 PID: 5286 at kernel/rcu/srcutree.c:456 srcu_readers_unlock_idx kernel/rcu/srcutree.c:455 [inline]
WARNING: CPU: 1 PID: 5286 at kernel/rcu/srcutree.c:456 srcu_readers_active_idx_check kernel/rcu/srcutree.c:468 [inline]
WARNING: CPU: 1 PID: 5286 at kernel/rcu/srcutree.c:456 try_check_zero+0x3b1/0x3e0 kernel/rcu/srcutree.c:1083
Modules linked in:
CPU: 1 UID: 0 PID: 5286 Comm: kworker/1:5 Not tainted 6.11.0-next-20240927-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 09/13/2024
Workqueue: rcu_gp process_srcu
RIP: 0010:srcu_readers_unlock_idx kernel/rcu/srcutree.c:455 [inline]
RIP: 0010:srcu_readers_active_idx_check kernel/rcu/srcutree.c:468 [inline]
RIP: 0010:try_check_zero+0x3b1/0x3e0 kernel/rcu/srcutree.c:1083
Code: 8b 3d b3 1a 19 0d e8 ae f2 48 0a e9 e5 fd ff ff c6 05 9e 22 8c 0e 01 90 48 c7 c7 20 12 0c 8c 48 8b 74 24 18 e8 c0 33 db ff 90 <0f> 0b 90 90 e9 e7 fe ff ff 49 39 cf 0f 94 c0 48 83 c4 30 5b 41 5c
RSP: 0018:ffffc9000421fa58 EFLAGS: 00010246
RAX: 860e4f5d8e8ca000 RBX: ffffe8ffffd35720 RCX: ffff88802d52bc00
RDX: 0000000000000000 RSI: 0000000000000001 RDI: 0000000000000000
RBP: ffffe8ffffd35718 R08: ffffffff8155d402 R09: fffffbfff1cf9fd8
R10: dffffc0000000000 R11: fffffbfff1cf9fd8 R12: ffffc900037148c0
R13: 0000000000000002 R14: dffffc0000000000 R15: 0000000000000003
FS:  0000000000000000(0000) GS:ffff8880b8700000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 000000002013c030 CR3: 0000000020f7c000 CR4: 00000000003526f0
DR0: 0000000000002800 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
Call Trace:
 <TASK>
 srcu_advance_state kernel/rcu/srcutree.c:1691 [inline]
 process_srcu+0x122/0x1320 kernel/rcu/srcutree.c:1818
 process_one_work kernel/workqueue.c:3229 [inline]
 process_scheduled_works+0xa63/0x1850 kernel/workqueue.c:3310
 worker_thread+0x870/0xd30 kernel/workqueue.c:3391
 kthread+0x2f0/0x390 kernel/kthread.c:389
 ret_from_fork+0x4b/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