syzbot


WARNING in rcu_sync_dtor (2)

Status: upstream: reported C repro on 2024/11/16 09:33
Subsystems: fs
[Documentation on labels]
Reported-by: syzbot+823cd0d24881f21ab9f1@syzkaller.appspotmail.com
First crash: 5d16h, last: 5d07h
Cause bisection: introduced by (bisect log) :
commit f761fcdd289d07e8547fef7ac76c3760fc7803f2
Author: Dongliang Cui <dongliang.cui@unisoc.com>
Date: Tue Sep 17 22:40:05 2024 +0000

  exfat: Implement sops->shutdown and ioctl

Crash: WARNING in rcu_sync_dtor (log)
Repro: C syz .config
  
Discussions (1)
Title Replies (including bot) Last reply
[syzbot] [fs?] WARNING in rcu_sync_dtor (2) 2 (5) 2024/11/17 00:46
Similar bugs (3)
Kernel Title Repro Cause bisect Fix bisect Count Last Reported Patched Status
linux-5.15 WARNING in rcu_sync_dtor origin:upstream C 157 32d 114d 0/3 upstream: reported C repro on 2024/07/26 22:24
upstream WARNING in rcu_sync_dtor f2fs C done 749 50d 114d 28/28 fixed on 2024/10/22 11:57
linux-6.1 WARNING in rcu_sync_dtor 1 65d 65d 0/3 upstream: reported on 2024/09/13 13:56
Last patch testing requests (2)
Created Duration User Patch Repo Result
2024/11/17 00:26 13m hdanton@sina.com patch upstream report log
2024/11/16 23:09 15m hdanton@sina.com patch upstream report log

Sample crash report:
------------[ cut here ]------------
WARNING: CPU: 0 PID: 9 at kernel/rcu/sync.c:177 rcu_sync_dtor+0xcd/0x180 kernel/rcu/sync.c:177
Modules linked in:
CPU: 0 UID: 0 PID: 9 Comm: kworker/0:1 Not tainted 6.12.0-rc7-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/30/2024
Workqueue: events destroy_super_work
RIP: 0010:rcu_sync_dtor+0xcd/0x180 kernel/rcu/sync.c:177
Code: 74 19 e8 96 dd 00 00 43 0f b6 44 25 00 84 c0 0f 85 82 00 00 00 41 83 3f 00 75 1d 5b 41 5c 41 5d 41 5e 41 5f c3 cc cc cc cc 90 <0f> 0b 90 e9 66 ff ff ff 90 0f 0b 90 eb 89 90 0f 0b 90 eb dd 44 89
RSP: 0018:ffffc900000e7b30 EFLAGS: 00010246

RAX: 0000000000000002 RBX: 1ffff1100fba4077 RCX: ffff88801d2b8000
RDX: 0000000000000000 RSI: ffffffff8c603640 RDI: ffff88807dd20350
RBP: 00000000000001e4 R08: ffffffff820ee1c4 R09: 1ffffffff1cfbc21
R10: dffffc0000000000 R11: fffffbfff1cfbc22 R12: dffffc0000000000
R13: 1ffff1100fba406a R14: ffff88807dd20350 R15: ffff88807dd20350
FS:  0000000000000000(0000) GS:ffff8880b8600000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000555567cdece8 CR3: 0000000030508000 CR4: 00000000003526f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
 <TASK>
 percpu_free_rwsem+0x41/0x80 kernel/locking/percpu-rwsem.c:42
 destroy_super_work+0xef/0x130 fs/super.c:282
 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>

Crashes (3):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2024/11/12 17:55 upstream 2d5404caa8c7 75bb1b32 .config console log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro #1] [mounted in repro #2] ci2-upstream-fs WARNING in rcu_sync_dtor
2024/11/12 14:05 upstream 2d5404caa8c7 75bb1b32 .config console log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro] ci2-upstream-fs WARNING in rcu_sync_dtor
2024/11/12 09:32 upstream 2d5404caa8c7 75bb1b32 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs WARNING in rcu_sync_dtor
* Struck through repros no longer work on HEAD.