From: syzbot <syzbot+eec8f2693d71386bd600@syzkaller.appspotmail.com>
To: chao@kernel.org, jaegeuk@kernel.org,
linux-f2fs-devel@lists.sourceforge.net,
linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com
Subject: [f2fs-dev] [syzbot] [f2fs?] INFO: trying to register non-static key in f2fs_exist_written_data
Date: Fri, 08 May 2026 16:03:22 -0700 [thread overview]
Message-ID: <69fe6bba.050a0220.1036b8.0004.GAE@google.com> (raw)
Hello,
syzbot found the following issue on:
HEAD commit: 9d0d467c3572 Add linux-next specific files for 20260504
git tree: linux-next
console output: https://syzkaller.appspot.com/x/log.txt?x=1654656a580000
kernel config: https://syzkaller.appspot.com/x/.config?x=ef1c15606892fce1
dashboard link: https://syzkaller.appspot.com/bug?extid=eec8f2693d71386bd600
compiler: Debian clang version 21.1.8 (++20251221033036+2078da43e25a-1~exp1~20251221153213.50), Debian LLD 21.1.8
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=157331ce580000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=161b4a73980000
Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/a19ae01a3069/disk-9d0d467c.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/29f12fe616bd/vmlinux-9d0d467c.xz
kernel image: https://storage.googleapis.com/syzbot-assets/eea74c667054/bzImage-9d0d467c.xz
mounted in repro: https://storage.googleapis.com/syzbot-assets/45693b275dc4/mount_0.gz
fsck result: failed (log: https://syzkaller.appspot.com/x/fsck.log?x=117331ce580000)
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+eec8f2693d71386bd600@syzkaller.appspotmail.com
F2FS-fs (loop0): Image doesn't support compression
F2FS-fs (loop0): invalid crc value
F2FS-fs (loop0): invalid crc value
F2FS-fs (loop0): Failed to get valid F2FS checkpoint
INFO: trying to register non-static key.
The code is fine but needs lockdep annotation, or maybe
you didn't initialize this object before use?
turning off the locking correctness validator.
CPU: 1 UID: 0 PID: 5928 Comm: syz.0.17 Not tainted syzkaller #0 PREEMPT_{RT,(full)}
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 04/18/2026
Call Trace:
<TASK>
dump_stack_lvl+0xe8/0x150 lib/dump_stack.c:120
assign_lock_key+0x133/0x150 kernel/locking/lockdep.c:986
register_lock_class+0xcc/0x2e0 kernel/locking/lockdep.c:1301
__lock_acquire+0xad/0x2d10 kernel/locking/lockdep.c:5114
lock_acquire+0x106/0x350 kernel/locking/lockdep.c:5870
rt_spin_lock+0x83/0x400 kernel/locking/spinlock_rt.c:56
spin_lock include/linux/spinlock_rt.h:45 [inline]
f2fs_exist_written_data+0x53/0x90 fs/f2fs/checkpoint.c:787
f2fs_drop_inode+0xda/0xbf0 fs/f2fs/super.c:1852
iput_final fs/inode.c:1926 [inline]
iput+0x651/0xe80 fs/inode.c:2009
f2fs_fill_super+0x6047/0x7850 fs/f2fs/super.c:5461
get_tree_bdev_flags+0x431/0x4f0 fs/super.c:1694
vfs_get_tree+0x92/0x2a0 fs/super.c:1754
fc_mount fs/namespace.c:1193 [inline]
do_new_mount_fc fs/namespace.c:3758 [inline]
do_new_mount+0x341/0xd30 fs/namespace.c:3834
do_mount fs/namespace.c:4167 [inline]
__do_sys_mount fs/namespace.c:4383 [inline]
__se_sys_mount+0x31d/0x420 fs/namespace.c:4360
do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
do_syscall_64+0x15f/0xf80 arch/x86/entry/syscall_64.c:94
entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7f39fca4e04a
Code: 48 c7 c2 e8 ff ff ff f7 d8 64 89 02 b8 ff ff ff ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 49 89 ca b8 a5 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 e8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007ffcfe531b98 EFLAGS: 00000246 ORIG_RAX: 00000000000000a5
RAX: ffffffffffffffda RBX: 00007ffcfe531c20 RCX: 00007f39fca4e04a
RDX: 0000200000000140 RSI: 00002000000000c0 RDI: 00007ffcfe531be0
RBP: 0000200000000140 R08: 00007ffcfe531c20 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 00002000000000c0
R13: 00007ffcfe531be0 R14: 0000000000005553 R15: 00002000000003c0
</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@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
_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
reply other threads:[~2026-05-08 23:03 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=69fe6bba.050a0220.1036b8.0004.GAE@google.com \
--to=syzbot+eec8f2693d71386bd600@syzkaller.appspotmail.com \
--cc=chao@kernel.org \
--cc=jaegeuk@kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=syzkaller-bugs@googlegroups.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox