linux-kernel - [syzbot] [ntfs3?] WARNING: locking bug in evict (2)

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives
Hash Suite for Android: free password hash cracker in your pocket
[<prev] [next>] [day] [month] [year] [list]
Message-ID: <000000000000100920061e5ced31@google.com>
Date: Sun, 28 Jul 2024 23:25:23 -0700
From: syzbot <syzbot+1b5e257b523f3e0be7d2@...kaller.appspotmail.com>
To: almaz.alexandrovich@...agon-software.com, linux-kernel@...r.kernel.org, 
	ntfs3@...ts.linux.dev, syzkaller-bugs@...glegroups.com
Subject: [syzbot] [ntfs3?] WARNING: locking bug in evict (2)

Hello,

syzbot found the following issue on:

HEAD commit:    d1e9a63dcd72 Merge tag 'vfs-6.11-rc1.fixes.2' of git://git..
git tree:       upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=165b609d980000
kernel config:  https://syzkaller.appspot.com/x/.config?x=8e1cc76f0e8412d3
dashboard link: https://syzkaller.appspot.com/bug?extid=1b5e257b523f3e0be7d2
compiler:       Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
syz repro:      https://syzkaller.appspot.com/x/repro.syz?x=157d7145980000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/8941969dc925/disk-d1e9a63d.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/0b29cfd6d8ee/vmlinux-d1e9a63d.xz
kernel image: https://storage.googleapis.com/syzbot-assets/106b1d908823/bzImage-d1e9a63d.xz
mounted in repro #1: https://storage.googleapis.com/syzbot-assets/e3d201c6ed53/mount_0.gz
mounted in repro #2: https://storage.googleapis.com/syzbot-assets/177c61e1ae2e/mount_7.gz

IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+1b5e257b523f3e0be7d2@...kaller.appspotmail.com

loop1: detected capacity change from 0 to 4096
------------[ cut here ]------------
DEBUG_LOCKS_WARN_ON(1)
WARNING: CPU: 0 PID: 5593 at kernel/locking/lockdep.c:231 hlock_class kernel/locking/lockdep.c:231 [inline]
WARNING: CPU: 0 PID: 5593 at kernel/locking/lockdep.c:231 check_wait_context kernel/locking/lockdep.c:4797 [inline]
WARNING: CPU: 0 PID: 5593 at kernel/locking/lockdep.c:231 __lock_acquire+0x925/0x2040 kernel/locking/lockdep.c:5092
Modules linked in:
CPU: 0 UID: 0 PID: 5593 Comm: syz.1.106 Not tainted 6.10.0-syzkaller-12261-gd1e9a63dcd72 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 06/27/2024
RIP: 0010:hlock_class kernel/locking/lockdep.c:231 [inline]
RIP: 0010:check_wait_context kernel/locking/lockdep.c:4797 [inline]
RIP: 0010:__lock_acquire+0x925/0x2040 kernel/locking/lockdep.c:5092
Code: 00 00 83 3d 8c ab 3e 0e 00 75 23 90 48 c7 c7 40 d4 ca 8b 48 c7 c6 e0 d6 ca 8b e8 e6 d5 e5 ff 48 ba 00 00 00 00 00 fc ff df 90 <0f> 0b 90 90 90 31 db 48 8d ab c4 00 00 00 48 89 e8 48 c1 e8 03 0f
RSP: 0018:ffffc900048d7650 EFLAGS: 00010046
RAX: c75590ab2862fe00 RBX: 0000000000001b00 RCX: ffff888026c0bc00
RDX: dffffc0000000000 RSI: 0000000000000000 RDI: 0000000000000000
RBP: 00000000ffffffff R08: ffffffff81559342 R09: 1ffff1101728519a
R10: dffffc0000000000 R11: ffffed101728519b R12: 0000000000000000
R13: ffff888026c0c6ff R14: 0000000000000000 R15: ffff888026c0c6ff
FS:  00007f25674c56c0(0000) GS:ffff8880b9400000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f2566759120 CR3: 000000005b364000 CR4: 00000000003506f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
 <TASK>
 lock_acquire+0x1ed/0x550 kernel/locking/lockdep.c:5759
 __raw_spin_lock include/linux/spinlock_api_smp.h:133 [inline]
 _raw_spin_lock+0x2e/0x40 kernel/locking/spinlock.c:154
 spin_lock include/linux/spinlock.h:351 [inline]
 inode_sb_list_del fs/inode.c:506 [inline]
 evict+0x161/0x630 fs/inode.c:658
 ntfs_fill_super+0x3e27/0x4730 fs/ntfs3/super.c:1467
 get_tree_bdev+0x3f7/0x570 fs/super.c:1624
 vfs_get_tree+0x90/0x2a0 fs/super.c:1789
 do_new_mount+0x2be/0xb40 fs/namespace.c:3472
 do_mount fs/namespace.c:3812 [inline]
 __do_sys_mount fs/namespace.c:4020 [inline]
 __se_sys_mount+0x2d6/0x3c0 fs/namespace.c:3997
 do_syscall_x64 arch/x86/entry/common.c:52 [inline]
 do_syscall_64+0xf3/0x230 arch/x86/entry/common.c:83
 entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7f256677761a
Code: d8 64 89 02 48 c7 c0 ff ff ff ff eb a6 e8 7e 1a 00 00 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 a8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007f25674c4e78 EFLAGS: 00000246 ORIG_RAX: 00000000000000a5
RAX: ffffffffffffffda RBX: 00007f25674c4f00 RCX: 00007f256677761a
RDX: 0000000020000080 RSI: 000000002001f740 RDI: 00007f25674c4ec0
RBP: 0000000020000080 R08: 00007f25674c4f00 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 000000002001f740
R13: 00007f25674c4ec0 R14: 000000000001f6fb R15: 00000000200000c0
 </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@...glegroups.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