[v6.1] WARNING in vfs_removexattr (2)

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: c63962be84ef Linux 6.1.124
git tree: linux-6.1.y
console output: https://syzkaller.appspot.com/x/log.txt?x=10c87ef8580000
kernel config: https://syzkaller.appspot.com/x/.config?x=b61d63ebcdeb2b69
dashboard link: https://syzkaller.appspot.com/bug?extid=b8679c99fc9a34969c2c
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/def628dfde4b/disk-c63962be.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/19bcf728ff3d/vmlinux-c63962be.xz
kernel image: https://storage.googleapis.com/syzbot-assets/dd43dbb11866/bzImage-c63962be.xz

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

DEBUG_RWSEMS_WARN_ON((rwsem_owner(sem) != current) && !rwsem_test_oflags(sem, RWSEM_NONSPINNABLE)): count = 0x0, magic = 0xffff888071945bb0, owner = 0x0, curr 0xffff88802b38d940, list empty
WARNING: CPU: 1 PID: 9631 at kernel/locking/rwsem.c:1372 __up_write kernel/locking/rwsem.c:1371 [inline]
WARNING: CPU: 1 PID: 9631 at kernel/locking/rwsem.c:1372 up_write+0x4f5/0x580 kernel/locking/rwsem.c:1626
Modules linked in:
CPU: 1 PID: 9631 Comm: syz.5.1819 Not tainted 6.1.124-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 09/13/2024
RIP: 0010:__up_write kernel/locking/rwsem.c:1371 [inline]
RIP: 0010:up_write+0x4f5/0x580 kernel/locking/rwsem.c:1626
Code: 48 c7 c7 e0 f6 0b 8b 48 c7 c6 20 f9 0b 8b 48 8b 54 24 28 48 8b 4c 24 18 4d 89 e0 4c 8b 4c 24 30 53 e8 ff c2 e8 ff 48 83 c4 08 <0f> 0b e9 71 fd ff ff 48 c7 c1 78 40 9b 8e 80 e1 07 80 c1 03 38 c1
RSP: 0018:ffffc900047efb20 EFLAGS: 00010292
RAX: fdd06c2ef6080600 RBX: ffffffff8b0bf7c0 RCX: 0000000000080000
RDX: ffffc9001b20d000 RSI: 00000000000096c7 RDI: 00000000000096c8
RBP: ffffc900047efbf0 R08: ffffffff8152b84e R09: fffffbfff2249c7a
R10: 0000000000000000 R11: dffffc0000000001 R12: 0000000000000000
R13: ffff888071945bb0 R14: 1ffff920008fdf6c R15: dffffc0000000000
FS: 00007f85962d56c0(0000) GS:ffff8880b8f00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000555579b1e5c8 CR3: 00000000278f8000 CR4: 00000000003506e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
inode_unlock include/linux/fs.h:763 [inline]
vfs_removexattr+0x10a/0x2a0 fs/xattr.c:538
removexattr fs/xattr.c:878 [inline]
path_removexattr+0x22a/0x320 fs/xattr.c:892
__do_sys_removexattr fs/xattr.c:906 [inline]
__se_sys_removexattr fs/xattr.c:903 [inline]
__x64_sys_removexattr+0x5c/0x70 fs/xattr.c:903
do_syscall_x64 arch/x86/entry/common.c:51 [inline]
do_syscall_64+0x3b/0xb0 arch/x86/entry/common.c:81
entry_SYSCALL_64_after_hwframe+0x68/0xd2
RIP: 0033:0x7f8595585d29
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:00007f85962d5038 EFLAGS: 00000246 ORIG_RAX: 00000000000000c5
RAX: ffffffffffffffda RBX: 00007f8595776080 RCX: 00007f8595585d29
RDX: 0000000000000000 RSI: 00000000200007c0 RDI: 0000000020000380
RBP: 00007f8595601b08 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 0000000000000001 R14: 00007f8595776080 R15: 00007ffe003ec0b8
</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

[syzbot]

Auto-closing this bug as obsolete.
Crashes did not happen for a while, no reproducer and no activity.

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 98f47d0e9b8c Linux 5.15.184
git tree: linux-5.15.y
console output: https://syzkaller.appspot.com/x/log.txt?x=1792ead4580000
kernel config: https://syzkaller.appspot.com/x/.config?x=9eb2b5a65dfc4761
dashboard link: https://syzkaller.appspot.com/bug?extid=c0c2c6f1dd865d654c31
compiler: Debian clang version 20.1.6 (++20250514063057+1e4d39e07757-1~exp1~20250514183223.118), Debian LLD 20.1.6
userspace arch: arm64

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

Downloadable assets:

disk image: https://storage.googleapis.com/syzbot-assets/d2845fb3af6c/disk-98f47d0e.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/1f12b743be24/vmlinux-98f47d0e.xz
kernel image: https://storage.googleapis.com/syzbot-assets/8f178b57ea38/Image-98f47d0e.gz.xz

IMPORTANT: if you fix the issue, please add the following tag to the commit:

Reported-by: syzbot+c0c2c6...@syzkaller.appspotmail.com

DEBUG_RWSEMS_WARN_ON((rwsem_owner(sem) != current) && !rwsem_test_oflags(sem, RWSEM_NONSPINNABLE)): count = 0x0, magic = 0xffff0000e9310330, owner = 0x0, curr 0xffff0000c770b680, list empty
WARNING: CPU: 1 PID: 7304 at kernel/locking/rwsem.c:1350 __up_write kernel/locking/rwsem.c:1349 [inline]
WARNING: CPU: 1 PID: 7304 at kernel/locking/rwsem.c:1350 up_write+0x4e8/0x644 kernel/locking/rwsem.c:1604
Modules linked in:
CPU: 1 PID: 7304 Comm: syz.3.988 Not tainted 5.15.184-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 05/07/2025
pstate: 60400005 (nZCv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--)
pc : __up_write kernel/locking/rwsem.c:1349 [inline]
pc : up_write+0x4e8/0x644 kernel/locking/rwsem.c:1604
lr : __up_write kernel/locking/rwsem.c:1349 [inline]
lr : up_write+0x4e8/0x644 kernel/locking/rwsem.c:1604
sp : ffff80001fef7a80
x29: ffff80001fef7a90 x28: ffff0000c770b680 x27: ffff80001fef7b40
x26: dfff800000000000 x25: 1fffe0001d262073 x24: ffff0000e9310388
x23: 0000000000000000 x22: 0000000000000000 x21: ffff0000c770b680
x20: ffff0000e9310330 x19: ffff0000e9310330 x18: 0000000000000002
x17: 0000000040000000 x16: ffff8000111a5644 x15: 0000000000000002
x14: 0000000000ff0100 x13: 1ffff0000282a06b x12: 0000000000080000
x11: 000000000000a210 x10: ffff800025639000 x9 : 275a22bb65781a00
x8 : 275a22bb65781a00 x7 : 0000000000000000 x6 : 0000000000000000
x5 : 0000000000000080 x4 : 0000000000000000 x3 : ffff80000850383c
x2 : 0000000000000001 x1 : 0000000100000000 x0 : 00000000000000bd
Call trace:
__up_write kernel/locking/rwsem.c:1349 [inline]
up_write+0x4e8/0x644 kernel/locking/rwsem.c:1604
inode_unlock include/linux/fs.h:792 [inline]
vfs_removexattr+0x8c/0x190 fs/xattr.c:529
removexattr fs/xattr.c:857 [inline]
path_removexattr+0x188/0x31c fs/xattr.c:871
__do_sys_removexattr fs/xattr.c:885 [inline]
__se_sys_removexattr fs/xattr.c:882 [inline]
__arm64_sys_removexattr+0x60/0x78 fs/xattr.c:882
__invoke_syscall arch/arm64/kernel/syscall.c:38 [inline]
invoke_syscall+0x98/0x2b8 arch/arm64/kernel/syscall.c:52
el0_svc_common+0x138/0x258 arch/arm64/kernel/syscall.c:142
do_el0_svc+0x58/0x14c arch/arm64/kernel/syscall.c:181
el0_svc+0x78/0x1e0 arch/arm64/kernel/entry-common.c:608
el0t_64_sync_handler+0xcc/0xe4 arch/arm64/kernel/entry-common.c:626
el0t_64_sync+0x1a0/0x1a4 arch/arm64/kernel/entry.S:584
irq event stamp: 506
hardirqs last enabled at (505): [<ffff800008244120>] raw_spin_rq_unlock_irq kernel/sched/sched.h:1338 [inline]
hardirqs last enabled at (505): [<ffff800008244120>] finish_lock_switch+0xb0/0x1c4 kernel/sched/core.c:4784
hardirqs last disabled at (506): [<ffff8000111a0f18>] el1_dbg+0x24/0x80 arch/arm64/kernel/entry-common.c:396
softirqs last enabled at (500): [<ffff80000819d0d8>] softirq_handle_end kernel/softirq.c:401 [inline]
softirqs last enabled at (500): [<ffff80000819d0d8>] handle_softirqs+0xa4c/0xbf0 kernel/softirq.c:586
softirqs last disabled at (185): [<ffff80000819d6dc>] __do_softirq kernel/softirq.c:592 [inline]
softirqs last disabled at (185): [<ffff80000819d6dc>] do_softirq_own_stack include/asm-generic/softirq_stack.h:10 [inline]
softirqs last disabled at (185): [<ffff80000819d6dc>] invoke_softirq kernel/softirq.c:439 [inline]
softirqs last disabled at (185): [<ffff80000819d6dc>] __irq_exit_rcu+0x240/0x440 kernel/softirq.c:641
---[ end trace 88f2b3d25f2b2956 ]---

[syzbot]