syzbot


WARNING: suspicious RCU usage in evict

Status: auto-obsoleted due to no activity on 2023/12/23 03:48
Subsystems: ntfs3
[Documentation on labels]
Reported-by: syzbot+45df7ccc8b5bade4f745@syzkaller.appspotmail.com
First crash: 550d, last: 297d
Cause bisection: introduced by (bisect log) :
commit 3eb8440d0d268437202ccbd28a3ca3212e02e57f
Author: Vijendar Mukunda <Vijendar.Mukunda@amd.com>
Date: Fri Jul 1 11:41:05 2022 +0000

  ASoC: amd: add I2S MICSP instance support

Crash: kernel panic: stack is corrupted in __lock_acquire (log)
Repro: C syz .config
  
Fix bisection: the issue occurs on the latest tested release (bisect log)
  
Discussions (1)
Title Replies (including bot) Last reply
[syzbot] WARNING: suspicious RCU usage in evict 0 (3) 2022/09/28 07:45
Last patch testing requests (5)
Created Duration User Patch Repo Result
2023/12/23 03:19 27m retest repro upstream OK log
2023/10/14 02:43 22m retest repro upstream report log
2023/09/09 06:44 31m retest repro upstream OK log
2023/08/05 01:37 21m retest repro upstream report log
2023/08/05 01:37 28m retest repro upstream OK log
Fix bisection attempts (7)
Created Duration User Patch Repo Result
2023/06/28 11:48 35m bisect fix upstream job log (0)
2023/05/26 17:48 30m bisect fix upstream job log (0) log
2023/04/26 15:28 34m bisect fix upstream job log (0) log
2023/03/27 10:44 29m bisect fix upstream job log (0) log
2023/02/24 23:29 30m bisect fix upstream job log (0) log
2023/01/25 22:53 36m bisect fix upstream job log (0) log
2022/11/07 22:49 30m bisect fix upstream job log (0) log

Sample crash report:
loop0: detected capacity change from 0 to 4096
ntfs3: loop0: Different NTFS' sector size (1024) and media sector size (512)
=============================
WARNING: suspicious RCU usage
6.0.0-syzkaller-00372-ga5088ee7251e #0 Not tainted
-----------------------------
include/trace/events/lock.h:69 suspicious rcu_dereference_check() usage!

other info that might help us debug this:


rcu_scheduler_active = 2, debug_locks = 1
2 locks held by syz-executor390/4555:
 #0: ffff88807690c0e0 (&type->s_umount_key#41/1){+.+.}-{3:3}, at: alloc_super+0x22e/0xb60 fs/super.c:228
 #1: ffff88807690c9d8 (&s->s_inode_list_lock){+.+.}-{2:2}, at: spin_lock include/linux/spinlock.h:349 [inline]
 #1: ffff88807690c9d8 (&s->s_inode_list_lock){+.+.}-{2:2}, at: inode_sb_list_del fs/inode.c:503 [inline]
 #1: ffff88807690c9d8 (&s->s_inode_list_lock){+.+.}-{2:2}, at: evict+0x179/0x6b0 fs/inode.c:654

stack backtrace:
CPU: 1 PID: 4555 Comm: syz-executor390 Not tainted 6.0.0-syzkaller-00372-ga5088ee7251e #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 09/22/2022
Call Trace:
 <TASK>
 __dump_stack lib/dump_stack.c:88 [inline]
 dump_stack_lvl+0xcd/0x134 lib/dump_stack.c:106
 trace_lock_release include/trace/events/lock.h:69 [inline]
 lock_release.cold+0x1f/0x4e kernel/locking/lockdep.c:5677
 __raw_spin_unlock include/linux/spinlock_api_smp.h:141 [inline]
 _raw_spin_unlock+0x12/0x40 kernel/locking/spinlock.c:186
 spin_unlock include/linux/spinlock.h:389 [inline]
 inode_sb_list_del fs/inode.c:505 [inline]
 evict+0x2aa/0x6b0 fs/inode.c:654
 iput_final fs/inode.c:1748 [inline]
 iput.part.0+0x55d/0x810 fs/inode.c:1774
 iput+0x58/0x70 fs/inode.c:1764
 ntfs_fill_super+0x2e89/0x37f0 fs/ntfs3/super.c:1190
 get_tree_bdev+0x440/0x760 fs/super.c:1323
 vfs_get_tree+0x89/0x2f0 fs/super.c:1530
 do_new_mount fs/namespace.c:3040 [inline]
 path_mount+0x1326/0x1e20 fs/namespace.c:3370
 do_mount fs/namespace.c:3383 [inline]
 __do_sys_mount fs/namespace.c:3591 [inline]
 __se_sys_mount fs/namespace.c:3568 [inline]
 __x64_sys_mount+0x27f/0x300 fs/namespace.c:3568
 do_syscall_x64 arch/x86/entry/common.c:50 [inline]
 do_syscall_64+0x35/0xb0 arch/x86/entry/common.c:80
 entry_SYSCALL_64_after_hwframe+0x63/0xcd
RIP: 0033:0x7f7fca475aaa
Code: 48 c7 c2 c0 ff ff ff f7 d8 64 89 02 b8 ff ff ff ff eb d2 e8 a8 00 00 00 0f 1f 84 00 00 00 00 00 49 89 ca b8 a5 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 c0 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007fff87884478 EFLAGS: 00000286 ORIG_RAX: 00000000000000a5
RAX: ffffffffffffffda RBX: 0000000000000003 RCX: 00007f7fca475aaa
RDX: 0000000020000000 RSI: 0000000020000100 RDI: 00007fff87884490
RBP: 00007fff87884490 R08: 00007fff878844d0 R09: 00007fff878844d0
R10: 0000000000000000 R11: 0000000000000286 R12: 0000000000000004
R13: 00007fff878844d0 R14: 000000000000010f R15: 0000000020001b68
 </TASK>
ntfs3: loop0: Mark volume as dirty due to NTFS errors
ntfs3: loop0: Failed to load $Extend.

Crashes (5):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2022/10/05 02:05 upstream a5088ee7251e eab8f949 .config console log report syz C [disk image] [vmlinux] [mounted in repro] ci-upstream-kasan-gce-root WARNING: suspicious RCU usage in evict
2022/09/28 07:44 upstream 46452d3786a8 75c78242 .config console log report syz C ci-upstream-kasan-gce-root WARNING: suspicious RCU usage in evict
2022/09/19 15:20 upstream 521a547ced64 dd9a85ff .config console log report syz ci-upstream-kasan-gce-root WARNING: suspicious RCU usage in evict
2022/09/16 22:44 upstream 6879c2d3b960 dd9a85ff .config console log report info [disk image] [vmlinux] ci-upstream-kasan-gce-root WARNING: suspicious RCU usage in evict
2022/09/15 09:32 upstream 3245cb65fd91 dd9a85ff .config console log report info ci-upstream-kasan-gce-root WARNING: suspicious RCU usage in evict
* Struck through repros no longer work on HEAD.