Hello,
syzbot found the following issue on:
HEAD commit: 91786f140358 Linux 5.15.175
git tree: linux-5.15.y
console output:
https://syzkaller.appspot.com/x/log.txt?x=17af46df980000
kernel config:
https://syzkaller.appspot.com/x/.config?x=1fc30776feb70ea7
dashboard link:
https://syzkaller.appspot.com/bug?extid=a575a5d54031731b70c4
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/210b1e4b59b1/disk-91786f14.raw.xz
vmlinux:
https://storage.googleapis.com/syzbot-assets/1cf8391059a0/vmlinux-91786f14.xz
kernel image:
https://storage.googleapis.com/syzbot-assets/1d9077a44b1c/bzImage-91786f14.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by:
syzbot+a575a5...@syzkaller.appspotmail.com
DEBUG_RWSEMS_WARN_ON((rwsem_owner(sem) != current) && !rwsem_test_oflags(sem, RWSEM_NONSPINNABLE)): count = 0x0, magic = 0xffff888052052f70, owner = 0x0, curr 0xffff888022ec9dc0, list empty
WARNING: CPU: 1 PID: 11433 at kernel/locking/rwsem.c:1350 __up_write kernel/locking/rwsem.c:1349 [inline]
WARNING: CPU: 1 PID: 11433 at kernel/locking/rwsem.c:1350 up_write+0x4f5/0x580 kernel/locking/rwsem.c:1604
Modules linked in:
CPU: 0 PID: 11433 Comm: syz.1.1078 Not tainted 5.15.175-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 09/13/2024
RIP: 0010:__up_write kernel/locking/rwsem.c:1349 [inline]
RIP: 0010:up_write+0x4f5/0x580 kernel/locking/rwsem.c:1604
Code: 48 c7 c7 00 1f ab 8a 48 c7 c6 c0 21 ab 8a 48 8b 54 24 28 48 8b 4c 24 18 4d 89 e0 4c 8b 4c 24 30 53 e8 9f 08 ea ff 48 83 c4 08 <0f> 0b e9 71 fd ff ff 48 c7 c1 18 94 0a 8e 80 e1 07 80 c1 03 38 c1
RSP: 0018:ffffc9000306fb80 EFLAGS: 00010292
RAX: eb0250f34acbf200 RBX: ffffffff8aab1fe0 RCX: 0000000000080000
RDX: ffffc90017c08000 RSI: 0000000000035137 RDI: 0000000000035138
RBP: ffffc9000306fc50 R08: ffffffff8166aa6c R09: ffffed10171e67a8
R10: 0000000000000000 R11: dffffc0000000001 R12: 0000000000000000
R13: ffff888052052f70 R14: 1ffff9200060df78 R15: dffffc0000000000
FS: 00007f13c77fb6c0(0000) GS:ffff8880b8f00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f4a480d3270 CR3: 0000000063121000 CR4: 00000000003506e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
inode_unlock include/linux/fs.h:794 [inline]
unlock_rename fs/namei.c:3065 [inline]
do_renameat2+0xea9/0x1700 fs/namei.c:4991
__do_sys_renameat2 fs/namei.c:5018 [inline]
__se_sys_renameat2 fs/namei.c:5015 [inline]
__x64_sys_renameat2+0xce/0xe0 fs/namei.c:5015
do_syscall_x64 arch/x86/entry/common.c:50 [inline]
do_syscall_64+0x3b/0xb0 arch/x86/entry/common.c:80
entry_SYSCALL_64_after_hwframe+0x66/0xd0
RIP: 0033:0x7f13c9a10d29
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:00007f13c77fb038 EFLAGS: 00000246 ORIG_RAX: 000000000000013c
RAX: ffffffffffffffda RBX: 00007f13c9c01080 RCX: 00007f13c9a10d29
RDX: 0000000000000008 RSI: 00000000200001c0 RDI: 0000000000000008
RBP: 00007f13c9a8cb08 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000020000180 R11: 0000000000000246 R12: 0000000000000000
R13: 0000000000000001 R14: 00007f13c9c01080 R15: 00007ffc712b15e8
</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