Hello,
syzbot found the following issue on:
HEAD commit: 50cbba13faa2 Linux 6.1.159
git tree: linux-6.1.y
console output:
https://syzkaller.appspot.com/x/log.txt?x=13d79b0a580000
kernel config:
https://syzkaller.appspot.com/x/.config?x=31ea1cecaf34f0db
dashboard link:
https://syzkaller.appspot.com/bug?extid=e3c6a20fde2a56b180df
compiler: Debian clang version 20.1.8 (++20250708063551+0c9f909b7976-1~exp1~20250708183702.136), Debian LLD 20.1.8
userspace arch: arm64
Unfortunately, I don't have any reproducer for this issue yet.
Downloadable assets:
disk image:
https://storage.googleapis.com/syzbot-assets/7ad0bd66715a/disk-50cbba13.raw.xz
vmlinux:
https://storage.googleapis.com/syzbot-assets/3284d626258e/vmlinux-50cbba13.xz
kernel image:
https://storage.googleapis.com/syzbot-assets/a1f92ca7bbfc/Image-50cbba13.gz.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by:
syzbot+e3c6a2...@syzkaller.appspotmail.com
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: 0 PID: 5405 Comm: syz.6.198 Not tainted syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/03/2025
Call trace:
dump_backtrace+0x1c8/0x1f4 arch/arm64/kernel/stacktrace.c:158
show_stack+0x2c/0x3c arch/arm64/kernel/stacktrace.c:165
__dump_stack+0x30/0x40 lib/dump_stack.c:88
dump_stack_lvl+0xf8/0x160 lib/dump_stack.c:106
dump_stack+0x1c/0x5c lib/dump_stack.c:113
assign_lock_key+0x224/0x258 kernel/locking/lockdep.c:974
register_lock_class+0x1ac/0x694 kernel/locking/lockdep.c:1287
__lock_acquire+0x150/0x6544 kernel/locking/lockdep.c:4928
lock_acquire+0x20c/0x644 kernel/locking/lockdep.c:5662
down_write+0x5c/0x88 kernel/locking/rwsem.c:1573
ntfs_set_size+0x130/0x200 fs/ntfs3/inode.c:845
ntfs_extend+0x130/0x444 fs/ntfs3/file.c:353
ntfs3_setattr+0x248/0x924 fs/ntfs3/file.c:712
notify_change+0xb0c/0xdcc fs/attr.c:499
do_truncate+0x178/0x1f0 fs/open.c:65
vfs_truncate+0x23c/0x2b0 fs/open.c:111
do_sys_truncate+0xe8/0x1b0 fs/open.c:134
__do_sys_truncate fs/open.c:146 [inline]
__se_sys_truncate fs/open.c:144 [inline]
__arm64_sys_truncate+0x5c/0x70 fs/open.c:144
__invoke_syscall arch/arm64/kernel/syscall.c:38 [inline]
invoke_syscall+0x98/0x2bc arch/arm64/kernel/syscall.c:52
el0_svc_common+0x138/0x258 arch/arm64/kernel/syscall.c:140
do_el0_svc+0x58/0x13c arch/arm64/kernel/syscall.c:204
el0_svc+0x58/0x138 arch/arm64/kernel/entry-common.c:637
el0t_64_sync_handler+0x84/0xf0 arch/arm64/kernel/entry-common.c:655
el0t_64_sync+0x18c/0x190 arch/arm64/kernel/entry.S:585
ntfs3: loop6: ino=19, "file1" attr_set_size
------------[ cut here ]------------
DEBUG_RWSEMS_WARN_ON(sem->magic != sem): count = 0x1, magic = 0x0, owner = 0xffff00010e04d340, curr 0xffff00010e04d340, list not empty
WARNING: CPU: 0 PID: 5405 at kernel/locking/rwsem.c:1366 __up_write kernel/locking/rwsem.c:1366 [inline]
WARNING: CPU: 0 PID: 5405 at kernel/locking/rwsem.c:1366 up_write+0x3b8/0x5c0 kernel/locking/rwsem.c:1626
Modules linked in:
CPU: 0 PID: 5405 Comm: syz.6.198 Not tainted syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/03/2025
pstate: 62400005 (nZCv daif +PAN -UAO +TCO -DIT -SSBS BTYPE=--)
pc : __up_write kernel/locking/rwsem.c:1366 [inline]
pc : up_write+0x3b8/0x5c0 kernel/locking/rwsem.c:1626
lr : __up_write kernel/locking/rwsem.c:1366 [inline]
lr : up_write+0x3b8/0x5c0 kernel/locking/rwsem.c:1626
sp : ffff800021987830
x29: ffff800021987840 x28: 1fffe0001f33ad3c x27: dfff800000000000
x26: dfff800000000000 x25: 0000000000000001 x24: ffff00010e04d340
x23: ffff00010e04d340 x22: 0000000000000000 x21: ffff0000f99d68d8
x20: ffff0000f99d68e8 x19: ffff0000f99d6880 x18: ffff800011a5bd40
x17: 1fffe00033ee7b7e x16: ffff800008042d90 x15: ffff80001504d000
x14: 0000000000000100 x13: 0000000000000120 x12: 0000000000000001
x11: 1fffe0001b112a90 x10: 0000000000000000 x9 : 9d718ce51d214e00
x8 : 9d718ce51d214e00 x7 : 0000000000000004 x6 : ffff8000082532dc
x5 : 0000000000000000 x4 : 0000000000000001 x3 : ffff800008242238
x2 : 0000000000000001 x1 : 0000000000000004 x0 : 0000000000000001
Call trace:
__up_write kernel/locking/rwsem.c:1366 [inline]
up_write+0x3b8/0x5c0 kernel/locking/rwsem.c:1626
ntfs_set_size+0x164/0x200 fs/ntfs3/inode.c:850
ntfs_extend+0x130/0x444 fs/ntfs3/file.c:353
ntfs3_setattr+0x248/0x924 fs/ntfs3/file.c:712
notify_change+0xb0c/0xdcc fs/attr.c:499
do_truncate+0x178/0x1f0 fs/open.c:65
vfs_truncate+0x23c/0x2b0 fs/open.c:111
do_sys_truncate+0xe8/0x1b0 fs/open.c:134
__do_sys_truncate fs/open.c:146 [inline]
__se_sys_truncate fs/open.c:144 [inline]
__arm64_sys_truncate+0x5c/0x70 fs/open.c:144
__invoke_syscall arch/arm64/kernel/syscall.c:38 [inline]
invoke_syscall+0x98/0x2bc arch/arm64/kernel/syscall.c:52
el0_svc_common+0x138/0x258 arch/arm64/kernel/syscall.c:140
do_el0_svc+0x58/0x13c arch/arm64/kernel/syscall.c:204
el0_svc+0x58/0x138 arch/arm64/kernel/entry-common.c:637
el0t_64_sync_handler+0x84/0xf0 arch/arm64/kernel/entry-common.c:655
el0t_64_sync+0x18c/0x190 arch/arm64/kernel/entry.S:585
irq event stamp: 15997
hardirqs last enabled at (15997): [<ffff8000083c0b24>] seqcount_lockdep_reader_access include/linux/seqlock.h:104 [inline]
hardirqs last enabled at (15997): [<ffff8000083c0b24>] ktime_get_coarse_real_ts64+0x114/0x244 kernel/time/timekeeping.c:2261
hardirqs last disabled at (15996): [<ffff8000083c0aac>] seqcount_lockdep_reader_access include/linux/seqlock.h:101 [inline]
hardirqs last disabled at (15996): [<ffff8000083c0aac>] ktime_get_coarse_real_ts64+0x9c/0x244 kernel/time/timekeeping.c:2261
softirqs last enabled at (15894): [<ffff8000080309e0>] local_bh_enable+0x10/0x34 include/linux/bottom_half.h:32
softirqs last disabled at (15892): [<ffff8000080309ac>] local_bh_disable+0x10/0x34 include/linux/bottom_half.h:19
---[ end trace 0000000000000000 ]---
---
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