Hello, syzbot found the following issue on: HEAD commit: 24ea63ea3877 Merge tag 'acpi-6.17-rc2' of git://git.kernel.. git tree: upstream console output: https://syzkaller.appspot.com/x/log.txt?x=13353da2580000 kernel config: https://syzkaller.appspot.com/x/.config?x=d67d3af29f50297e dashboard link: https://syzkaller.appspot.com/bug?extid=5ce48a14916462cec450 compiler: Debian clang version 20.1.7 (++20250616065708+6146a88f6049-1~exp1~20250616065826.132), Debian LLD 20.1.7 syz repro: https://syzkaller.appspot.com/x/repro.syz?x=100883a2580000 C reproducer: https://syzkaller.appspot.com/x/repro.c?x=1329d842580000 Downloadable assets: disk image (non-bootable): https://storage.googleapis.com/syzbot-assets/d900f083ada3/non_bootable_disk-24ea63ea.raw.xz vmlinux: https://storage.googleapis.com/syzbot-assets/307e082b78f2/vmlinux-24ea63ea.xz kernel image: https://storage.googleapis.com/syzbot-assets/a771414670e3/bzImage-24ea63ea.xz mounted in repro: https://storage.googleapis.com/syzbot-assets/6d33fef85cee/mount_0.gz fsck result: OK (log: https://syzkaller.appspot.com/x/fsck.log?x=15353da2580000) IMPORTANT: if you fix the issue, please add the following tag to the commit: Reported-by: syzbot+5ce48a14916462cec450@xxxxxxxxxxxxxxxxxxxxxxxxx ------------[ cut here ]------------ DEBUG_RWSEMS_WARN_ON((rwsem_owner(sem) != current) && !rwsem_test_oflags(sem, RWSEM_NONSPINNABLE)): count = 0x0, magic = 0xffff8880422768f8, owner = 0x0, curr 0xffff88803304c880, list empty WARNING: CPU: 0 PID: 5726 at kernel/locking/rwsem.c:1381 __up_write kernel/locking/rwsem.c:1380 [inline] WARNING: CPU: 0 PID: 5726 at kernel/locking/rwsem.c:1381 up_write+0x3a2/0x420 kernel/locking/rwsem.c:1643 Modules linked in: CPU: 0 UID: 0 PID: 5726 Comm: syz.0.47 Not tainted 6.17.0-rc1-syzkaller-00111-g24ea63ea3877 #0 PREEMPT(full) Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-debian-1.16.3-2~bpo12+1 04/01/2014 RIP: 0010:__up_write kernel/locking/rwsem.c:1380 [inline] RIP: 0010:up_write+0x3a2/0x420 kernel/locking/rwsem.c:1643 Code: d0 48 c7 c7 60 ec 8a 8b 48 c7 c6 80 ee 8a 8b 48 8b 14 24 4c 89 f1 4d 89 e0 4c 8b 4c 24 08 41 52 e8 d3 56 e6 ff 48 83 c4 08 90 <0f> 0b 90 90 e9 6d fd ff ff 48 c7 c1 74 cf a3 8f 80 e1 07 80 c1 03 RSP: 0018:ffffc9000d99fa50 EFLAGS: 00010296 RAX: 1cf7ff1b0c410100 RBX: ffff8880422768f8 RCX: ffff88803304c880 RDX: 0000000000000000 RSI: 0000000000000001 RDI: 0000000000000002 RBP: dffffc0000000000 R08: ffff88801fc24253 R09: 1ffff11003f8484a R10: dffffc0000000000 R11: ffffed1003f8484b R12: 0000000000000000 R13: ffff888042276950 R14: ffff8880422768f8 R15: 1ffff1100844ed20 FS: 00007f3d8169c6c0(0000) GS:ffff88808d210000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 00007f3d8169bfc8 CR3: 0000000033237000 CR4: 0000000000352ef0 Call Trace: <TASK> inode_unlock include/linux/fs.h:879 [inline] vfs_setxattr+0x17a/0x2f0 fs/xattr.c:323 do_setxattr fs/xattr.c:636 [inline] filename_setxattr+0x274/0x600 fs/xattr.c:665 path_setxattrat+0x364/0x3a0 fs/xattr.c:713 __do_sys_setxattr fs/xattr.c:747 [inline] __se_sys_setxattr fs/xattr.c:743 [inline] __x64_sys_setxattr+0xbc/0xe0 fs/xattr.c:743 do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline] do_syscall_64+0xfa/0x3b0 arch/x86/entry/syscall_64.c:94 entry_SYSCALL_64_after_hwframe+0x77/0x7f RIP: 0033:0x7f3d8078ebe9 Code: ff ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 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 a8 ff ff ff f7 d8 64 89 01 48 RSP: 002b:00007f3d8169c038 EFLAGS: 00000246 ORIG_RAX: 00000000000000bc RAX: ffffffffffffffda RBX: 00007f3d809b6090 RCX: 00007f3d8078ebe9 RDX: 0000200000000100 RSI: 0000200000000540 RDI: 00002000000003c0 RBP: 00007f3d80811e19 R08: 0000000000000001 R09: 0000000000000000 R10: 00000000000000a6 R11: 0000000000000246 R12: 0000000000000000 R13: 00007f3d809b6128 R14: 00007f3d809b6090 R15: 00007ffdbb0ae248 </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@xxxxxxxxxxxxxxxx. 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
