From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mail-oi1-f205.google.com (mail-oi1-f205.google.com [209.85.167.205]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id AEEDE44E666 for ; Mon, 17 Aug 2026 17:18:27 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=209.85.167.205 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1786987109; cv=none; b=gLoGGZr3OV0AxyDziVgR/E+RX8l1bEZbHiYoHgAmUsOsxBRumNzZgZFTQMK21P3ZcxHSUZxYXu2JKR95k2vqk5W54X8E4HumPFlRmUhdfmn3n8PQ1Z5WsH/Oyzo6Mvwa5F2c2/sl070Vp+hOS4tnRkkm+bc8yCrCe6jh2s/EA9c= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1786987109; c=relaxed/simple; bh=EJvaL2SNfcbMEq698oKZ7tqRLj2qNaZBgOV3R8OmzPU=; h=MIME-Version:Date:Message-ID:Subject:From:To:Content-Type; b=M56KoDOkvi/gPFAi95l4yXoR20KUATQ/I9W4TLNkzEW6q4iP9uvFd/qtAxw04Nr4mCcs9vZeS7DhtZcvjOSELqZtLv+n0oiyBOmdnnVfx/P6IXmlGsddWUrm2aa5w9CCDfyg+/SWZF5fbVoMGYN4shpfZvOJhocB1Dm0jwqzzuM= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=fail (p=none dis=none) header.from=syzkaller.appspotmail.com; spf=pass smtp.mailfrom=M3KW2WVRGUFZ5GODRSRYTGD7.apphosting.bounces.google.com; arc=none smtp.client-ip=209.85.167.205 Authentication-Results: smtp.subspace.kernel.org; dmarc=fail (p=none dis=none) header.from=syzkaller.appspotmail.com Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=M3KW2WVRGUFZ5GODRSRYTGD7.apphosting.bounces.google.com Received: by mail-oi1-f205.google.com with SMTP id 5614622812f47-4b26d8d2498so2478483b6e.2 for ; Mon, 17 Aug 2026 10:18:27 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20251104; t=1786987106; x=1787591906; h=content-type:to:from:subject:message-id:date:mime-version :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to :content-type; bh=ld6FH4QpO5L065SRwsrRGyQwH2sHUvD5cM4LrAxxHZc=; b=S8NLbDBX8eiFpR0Qg05uwTvi+0YQ+bUqZVTW6wKr+wux3+Mrz2jDj4gLG0TZ1sZtl2 E4sB/+ujka580KdbtgIpqkD2jYMWb4UNuGtiesdLmEvtN0DJJWyBhBBUWnHcvW6ZxWdw w2EwplLXk12pj6PrG8ydt2MVVUfa6G5L0Ll9Jix5MRZrdhrzRxdLzSGbsCi+sQV3ydBV vrnNHRLr1+kcjSRUe9oGrS2RE7s+Ts1/QcP64Dv0rvG9h8Ayx+rVYJdi+aIegN9Jaohv 76INyJCdEck5Tq8Sf5ztGvd4q6YhkakBB2GQThjC01R7sVDyyTJcbrgh3bweb21IGZBo v+MQ== X-Forwarded-Encrypted: i=1; AHgh+Ro7rl+EKDG2vU+sKPKYa3Vu1Mtk3CdRPY5MkDXF2VJU2wrGwkNQYCleMP96FmMXiLZR3iltLeG1j5tzqMM=@vger.kernel.org X-Gm-Message-State: AOJu0YyvGCGLh6DihSoQrWpwuuGjPw1YgaZZ+4Wkkq/2QO46mtZfNr5n wWcj46twDrRx3F67+yv1g5MhYX4qEdlzmzb9ZushoVSXjcJfO3mDIQO1apWNGugo8IDfsrXVkN7 qwYPx4KVTaZuOAy9ZUztMSTFo6rdScMDSQsWpNK+sMRqgcy+PfgBBxTnn69c= Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 X-Received: by 2002:a05:6808:c3ec:b0:4aa:cad:cb4c with SMTP id 5614622812f47-4b240f875b2mr22702284b6e.1.1786987106545; Mon, 17 Aug 2026 10:18:26 -0700 (PDT) Date: Mon, 17 Aug 2026 10:18:26 -0700 X-Google-Appengine-App-Id: s~syzkaller X-Google-Appengine-App-Id-Alias: syzkaller Message-ID: <6a834262.4d75e56a.c9a88.0002.GAE@google.com> Subject: [syzbot] [f2fs?] WARNING: suspicious RCU usage in __f2fs_add_ino_entry From: syzbot To: chao@kernel.org, jaegeuk@kernel.org, linux-f2fs-devel@lists.sourceforge.net, linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com Content-Type: text/plain; charset="UTF-8" Hello, syzbot found the following issue on: HEAD commit: 4477a78374a5 Add linux-next specific files for 20260814 git tree: linux-next console output: https://syzkaller.appspot.com/x/log.txt?x=150bea25580000 kernel config: https://syzkaller.appspot.com/x/.config?x=9b32a36dd637b06f dashboard link: https://syzkaller.appspot.com/bug?extid=014a7b70788139e6196d compiler: Debian clang version 22.1.8 (++20260613092233+e80beda6e255-1~exp1~20260613092250.77), Debian LLD 22.1.8 syz repro: https://syzkaller.appspot.com/x/repro.syz?x=12d3fa79580000 Downloadable assets: disk image: https://storage.googleapis.com/syzbot-assets/994c1c8c560e/disk-4477a783.raw.xz vmlinux: https://storage.googleapis.com/syzbot-assets/cd54543d69ae/vmlinux-4477a783.xz kernel image: https://storage.googleapis.com/syzbot-assets/407cdf8f3fc2/bzImage-4477a783.xz mounted in repro: https://storage.googleapis.com/syzbot-assets/12687adce9ef/mount_0.gz fsck result: failed (log: https://syzkaller.appspot.com/x/fsck.log?x=171cd949580000) IMPORTANT: if you fix the issue, please add the following tag to the commit: Reported-by: syzbot+014a7b70788139e6196d@syzkaller.appspotmail.com ============================= WARNING: suspicious RCU usage syzkaller #0 Not tainted ----------------------------- ./include/linux/radix-tree.h:179 suspicious rcu_dereference_check() usage! other info that might help us debug this: rcu_scheduler_active = 2, debug_locks = 1 locks held by kworker/u9:3/5775: 4, last CPU#0: #0: ffff88807f597940 ((wq_completion)f2fs_evict_wq){+.+.}-{0:0}, at: rcu_lock_acquire include/linux/rcupdate.h:309 [inline] #0: ffff88807f597940 ((wq_completion)f2fs_evict_wq){+.+.}-{0:0}, at: rcu_read_lock include/linux/rcupdate.h:849 [inline] #0: ffff88807f597940 ((wq_completion)f2fs_evict_wq){+.+.}-{0:0}, at: process_one_work kernel/workqueue.c:3352 [inline] #0: ffff88807f597940 ((wq_completion)f2fs_evict_wq){+.+.}-{0:0}, at: process_scheduled_works+0x97a/0x1630 kernel/workqueue.c:3470 #1: ffffc90003fb7c40 ((work_completion)(&ew->work)){+.+.}-{0:0}, at: rcu_lock_acquire include/linux/rcupdate.h:309 [inline] #1: ffffc90003fb7c40 ((work_completion)(&ew->work)){+.+.}-{0:0}, at: rcu_read_lock include/linux/rcupdate.h:849 [inline] #1: ffffc90003fb7c40 ((work_completion)(&ew->work)){+.+.}-{0:0}, at: process_one_work kernel/workqueue.c:3352 [inline] #1: ffffc90003fb7c40 ((work_completion)(&ew->work)){+.+.}-{0:0}, at: process_scheduled_works+0x97a/0x1630 kernel/workqueue.c:3470 #2: ffff8880b863a820 (lock){+.+.}-{3:3}, at: local_lock_acquire include/linux/local_lock_internal.h:46 [inline] #2: ffff8880b863a820 (lock){+.+.}-{3:3}, at: __radix_tree_preload+0x82/0x870 lib/radix-tree.c:334 #3: ffff8880338688c8 (&im->ino_lock){+.+.}-{3:3}, at: spin_lock include/linux/spinlock.h:347 [inline] #3: ffff8880338688c8 (&im->ino_lock){+.+.}-{3:3}, at: __set_ino_bitmap fs/f2fs/checkpoint.c:781 [inline] #3: ffff8880338688c8 (&im->ino_lock){+.+.}-{3:3}, at: __f2fs_add_ino_entry+0x14c/0x830 fs/f2fs/checkpoint.c:842 stack backtrace: CPU: 0 UID: 0 PID: 5775 Comm: kworker/u9:3 Not tainted syzkaller #0 PREEMPT(full) Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/24/2026 Workqueue: f2fs_evict_wq f2fs_evict_inode_work Call Trace: dump_stack_lvl+0xe8/0x150 lib/dump_stack.c:120 lockdep_rcu_suspicious+0x140/0x1d0 kernel/locking/lockdep.c:6938 radix_tree_deref_slot include/linux/radix-tree.h:179 [inline] __set_ino_bitmap fs/f2fs/checkpoint.c:784 [inline] __f2fs_add_ino_entry+0x782/0x830 fs/f2fs/checkpoint.c:842 f2fs_record_inode_state fs/f2fs/inode.c:877 [inline] f2fs_evict_inode_work+0xa1/0x120 fs/f2fs/inode.c:887 process_one_work kernel/workqueue.c:3387 [inline] process_scheduled_works+0xc3d/0x1630 kernel/workqueue.c:3470 worker_thread+0xa47/0xfb0 kernel/workqueue.c:3551 kthread+0x38b/0x480 kernel/kthread.c:436 ret_from_fork+0x514/0xb70 arch/x86/kernel/process.c:158 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:245 --- 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@googlegroups.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