[<prev] [next>] [day] [month] [year] [list]
Message-ID: <6768a456.050a0220.2f3838.000e.GAE@google.com>
Date: Sun, 22 Dec 2024 15:44:22 -0800
From: syzbot <syzbot+cf9a826a13c8657c38e9@...kaller.appspotmail.com>
To: bp@...en8.de, dave.hansen@...ux.intel.com, hpa@...or.com,
kent.overstreet@...ux.dev, linux-bcachefs@...r.kernel.org,
linux-kernel@...r.kernel.org, mingo@...hat.com,
syzkaller-bugs@...glegroups.com, tglx@...utronix.de, x86@...nel.org
Subject: [syzbot] [bcachefs?] WARNING in try_check_zero (3)
Hello,
syzbot found the following issue on:
HEAD commit: eabcdba3ad40 Merge tag 'for-6.13-rc3-tag' of git://git.ker..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=12514cf8580000
kernel config: https://syzkaller.appspot.com/x/.config?x=1234f097ee657d8b
dashboard link: https://syzkaller.appspot.com/bug?extid=cf9a826a13c8657c38e9
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=160d22df980000
Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/7a4dff87674a/disk-eabcdba3.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/266bc2b7ced3/vmlinux-eabcdba3.xz
kernel image: https://storage.googleapis.com/syzbot-assets/ee4bcd9be832/bzImage-eabcdba3.xz
mounted in repro: https://storage.googleapis.com/syzbot-assets/7cb3486c31c1/mount_0.gz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+cf9a826a13c8657c38e9@...kaller.appspotmail.com
------------[ cut here ]------------
Mixed reader flavors for srcu_struct at 0xffff888068604388.
WARNING: CPU: 1 PID: 5992 at kernel/rcu/srcutree.c:474 srcu_readers_unlock_idx kernel/rcu/srcutree.c:473 [inline]
WARNING: CPU: 1 PID: 5992 at kernel/rcu/srcutree.c:474 srcu_readers_active_idx_check kernel/rcu/srcutree.c:489 [inline]
WARNING: CPU: 1 PID: 5992 at kernel/rcu/srcutree.c:474 try_check_zero+0x45a/0x4a0 kernel/rcu/srcutree.c:1108
Modules linked in:
CPU: 1 UID: 0 PID: 5992 Comm: kworker/1:4 Not tainted 6.13.0-rc3-syzkaller-00073-geabcdba3ad40 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 11/25/2024
Workqueue: rcu_gp process_srcu
RIP: 0010:srcu_readers_unlock_idx kernel/rcu/srcutree.c:473 [inline]
RIP: 0010:srcu_readers_active_idx_check kernel/rcu/srcutree.c:489 [inline]
RIP: 0010:try_check_zero+0x45a/0x4a0 kernel/rcu/srcutree.c:1108
Code: 8b 3d 7a c6 0e 0d e8 85 78 3a 0a e9 55 fd ff ff c6 05 01 99 7d 0e 01 90 48 c7 c7 c0 d6 0b 8c 48 8b 74 24 08 e8 67 28 db ff 90 <0f> 0b 90 90 e9 57 fe ff ff c6 05 df 98 7d 0e 01 90 48 c7 c7 c0 d6
RSP: 0018:ffffc900034efa50 EFLAGS: 00010246
RAX: 3561385088340b00 RBX: ffffe8ffffd57820 RCX: ffff888075a45a00
RDX: 0000000000000000 RSI: 0000000000000001 RDI: 0000000000000000
RBP: dffffc0000000000 R08: ffffffff81601962 R09: fffffbfff1cfa210
R10: dffffc0000000000 R11: fffffbfff1cfa210 R12: ffff888068604390
R13: 0000000000000002 R14: 0000000000000000 R15: 0000000000000009
FS: 0000000000000000(0000) GS:ffff8880b8700000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007fee10b2d000 CR3: 000000003263a000 CR4: 00000000003526f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
srcu_advance_state kernel/rcu/srcutree.c:1724 [inline]
process_srcu+0x11f/0x12e0 kernel/rcu/srcutree.c:1851
process_one_work kernel/workqueue.c:3229 [inline]
process_scheduled_works+0xa66/0x1840 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 syzbot to run the reproducer, reply with:
#syz test: git://repo/address.git branch-or-commit-hash
If you attach or paste a git patch, syzbot will apply it before testing.
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