[v6.1] WARNING in validate_chain

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 347385861c50 Linux 6.1.84
git tree: linux-6.1.y
console output: https://syzkaller.appspot.com/x/log.txt?x=1055c5a1180000
kernel config: https://syzkaller.appspot.com/x/.config?x=40dfd13b04bfc094
dashboard link: https://syzkaller.appspot.com/bug?extid=6315b870b87a3d2fa0c7
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40

Unfortunately, I don't have any reproducer for this issue yet.

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/584c64d6360b/disk-34738586.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/ebe1b8334610/vmlinux-34738586.xz
kernel image: https://storage.googleapis.com/syzbot-assets/e3d485b54a02/bzImage-34738586.xz

IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+6315b8...@syzkaller.appspotmail.com

------------[ cut here ]------------
DEBUG_LOCKS_WARN_ON(!irqs_disabled())
WARNING: CPU: 1 PID: 5453 at kernel/locking/lockdep.c:150 lockdep_unlock+0x1e2/0x300 kernel/locking/lockdep.c:150
Modules linked in:
CPU: 1 PID: 5453 Comm: syz-executor.4 Not tainted 6.1.84-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 03/27/2024
RIP: 0010:lockdep_unlock+0x1e2/0x300 kernel/locking/lockdep.c:150
Code: 04 30 84 c0 0f 85 e5 00 00 00 83 3d 8f 8f 09 0d 00 0f 85 ef fe ff ff 48 c7 c7 60 ed eb 8a 48 c7 c6 a0 ed eb 8a e8 ae 6c e8 ff <0f> 0b e9 d5 fe ff ff e8 b2 ab ca 02 85 c0 0f 84 76 ff ff ff 48 c7
RSP: 0018:ffffc90004297600 EFLAGS: 00010246
RAX: aaace708aea74200 RBX: 1ffff92000852ec4 RCX: 0000000000040000
RDX: ffffc90003a91000 RSI: 0000000000003614 RDI: 0000000000003615
RBP: ffffc90004297690 R08: ffffffff81527eae R09: ffffed1017324f1c
R10: 0000000000000000 R11: dffffc0000000001 R12: 1ffff92000852ec0
R13: ffff88807ed80ba0 R14: dffffc0000000000 R15: ffffc90004297620
FS: 00007f5805fb96c0(0000) GS:ffff8880b9900000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f29081025a1 CR3: 00000000276e2000 CR4: 00000000003506e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
graph_unlock kernel/locking/lockdep.c:186 [inline]
validate_chain+0x13ce/0x5950 kernel/locking/lockdep.c:3829
__lock_acquire+0x125b/0x1f80 kernel/locking/lockdep.c:5049
lock_acquire+0x1f8/0x5a0 kernel/locking/lockdep.c:5662
__raw_spin_lock include/linux/spinlock_api_smp.h:133 [inline]
_raw_spin_lock+0x2a/0x40 kernel/locking/spinlock.c:154
spin_lock include/linux/spinlock.h:351 [inline]
inode_sb_list_add fs/inode.c:495 [inline]
iget_locked+0x618/0x830 fs/inode.c:1343
kernfs_get_inode+0x4c/0x6b0 fs/kernfs/inode.c:254
kernfs_iop_lookup+0x265/0x380 fs/kernfs/dir.c:1178
lookup_one_qstr_excl+0x117/0x240 fs/namei.c:1605
filename_create+0x293/0x530 fs/namei.c:3879
do_mkdirat+0xba/0x360 fs/namei.c:4123
__do_sys_mkdirat fs/namei.c:4148 [inline]
__se_sys_mkdirat fs/namei.c:4146 [inline]
__x64_sys_mkdirat+0x85/0x90 fs/namei.c:4146
do_syscall_x64 arch/x86/entry/common.c:51 [inline]
do_syscall_64+0x3d/0xb0 arch/x86/entry/common.c:81
entry_SYSCALL_64_after_hwframe+0x63/0xcd
RIP: 0033:0x7f580527de69
Code: 28 00 00 00 75 05 48 83 c4 28 c3 e8 e1 20 00 00 90 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 b0 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007f5805fb90c8 EFLAGS: 00000246 ORIG_RAX: 0000000000000102
RAX: ffffffffffffffda RBX: 00007f58053abf80 RCX: 00007f580527de69
RDX: 00000000000001ff RSI: 0000000020000000 RDI: ffffffffffffff9c
RBP: 00007f58052ca47a R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 000000000000000b R14: 00007f58053abf80 R15: 00007fff4cd51888
</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 syzk...@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 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