[fs?] WARNING in do_linkat

4 views
Skip to first unread message

syzbot

unread,
Feb 26, 2023, 12:56:40 PM2/26/23
to syzkaller-upst...@googlegroups.com
Hello,

syzbot found the following issue on:

HEAD commit: 5b7c4cabbb65 Merge tag 'net-next-6.3' of git://git.kernel...
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=1352d0a8c80000
kernel config: https://syzkaller.appspot.com/x/.config?x=5f796d50141fdd96
dashboard link: https://syzkaller.appspot.com/bug?extid=d1566ad5ad7be1af2919
compiler: Debian clang version 15.0.7, GNU ld (GNU Binutils for Debian) 2.35.2
CC: [linux-...@vger.kernel.org linux-...@vger.kernel.org vi...@zeniv.linux.org.uk]

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/a3a9a596f950/disk-5b7c4cab.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/a3280854515f/vmlinux-5b7c4cab.xz
kernel image: https://storage.googleapis.com/syzbot-assets/6cd84c50054b/bzImage-5b7c4cab.xz

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

------------[ cut here ]------------
DEBUG_RWSEMS_WARN_ON((rwsem_owner(sem) != current) && !rwsem_test_oflags(sem, RWSEM_NONSPINNABLE)): count = 0x0, magic = 0xffff888079c6d450, owner = 0x0, curr 0xffff888020cb0000, list empty
WARNING: CPU: 0 PID: 6033 at kernel/locking/rwsem.c:1370 __up_write kernel/locking/rwsem.c:1369 [inline]
WARNING: CPU: 0 PID: 6033 at kernel/locking/rwsem.c:1370 up_write+0x4f4/0x580 kernel/locking/rwsem.c:1626
Modules linked in:
CPU: 0 PID: 6033 Comm: syz-executor.5 Not tainted 6.2.0-syzkaller-05251-g5b7c4cabbb65 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/21/2023
RIP: 0010:__up_write kernel/locking/rwsem.c:1369 [inline]
RIP: 0010:up_write+0x4f4/0x580 kernel/locking/rwsem.c:1626
Code: 48 c7 c7 60 6f ea 8a 48 c7 c6 00 72 ea 8a 48 8b 54 24 28 48 8b 4c 24 18 4d 89 e0 4c 8b 4c 24 30 53 e8 e0 4e e8 ff 48 83 c4 08 <0f> 0b e9 75 fd ff ff 48 c7 c1 18 9f 53 8e 80 e1 07 80 c1 03 38 c1
RSP: 0018:ffffc9001572fce0 EFLAGS: 00010292
RAX: f615e8d485162e00 RBX: ffffffff8aea7040 RCX: 0000000000040000
RDX: ffffc9000cb1c000 RSI: 000000000000f6fb RDI: 000000000000f6fc
RBP: ffffc9001572fdb0 R08: ffffffff81536d42 R09: fffff52002ae5f15
R10: 0000000000000000 R11: dffffc0000000001 R12: 0000000000000000
R13: ffff888079c6d450 R14: 1ffff92002ae5fa4 R15: dffffc0000000000
FS: 00007f9192d05700(0000) GS:ffff8880b9800000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007fc453ddd800 CR3: 000000002ad8c000 CR4: 00000000003506f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
inode_unlock include/linux/fs.h:761 [inline]
done_path_create fs/namei.c:3858 [inline]
do_linkat+0x34f/0x9e0 fs/namei.c:4596
__do_sys_link fs/namei.c:4627 [inline]
__se_sys_link fs/namei.c:4625 [inline]
__x64_sys_link+0x86/0x90 fs/namei.c:4625
do_syscall_x64 arch/x86/entry/common.c:50 [inline]
do_syscall_64+0x41/0xc0 arch/x86/entry/common.c:80
entry_SYSCALL_64_after_hwframe+0x63/0xcd
RIP: 0033:0x7f919208c0f9
Code: 28 00 00 00 75 05 48 83 c4 28 c3 e8 f1 19 00 00 90 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 b8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007f9192d05168 EFLAGS: 00000246 ORIG_RAX: 0000000000000056
RAX: ffffffffffffffda RBX: 00007f91921abf80 RCX: 00007f919208c0f9
RDX: 0000000000000000 RSI: 0000000020000140 RDI: 0000000020000100
RBP: 00007f91920e7ae9 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007fff626f203f R14: 00007f9192d05300 R15: 0000000000022000
</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.

syzbot

unread,
May 23, 2023, 1:49:50 PM5/23/23
to syzkaller-upst...@googlegroups.com
Auto-closing this bug as obsolete.
Crashes did not happen for a while, no reproducer and no activity.
Reply all
Reply to author
Forward
0 new messages