[v6.1] WARNING in path_openat (5)

0 views
Skip to first unread message

syzbot

unread,
1:07 AM (16 hours ago) 1:07 AM
to syzkaller...@googlegroups.com
Hello,

syzbot found the following issue on:

HEAD commit: fb28aa725e05 Linux 6.1.180
git tree: linux-6.1.y
console output: https://syzkaller.appspot.com/x/log.txt?x=100ecbb9580000
kernel config: https://syzkaller.appspot.com/x/.config?x=31dfefc4a14efea3
dashboard link: https://syzkaller.appspot.com/bug?extid=ef6c9dd6b509d468116e
compiler: Debian clang version 22.1.8 (++20260613092233+e80beda6e255-1~exp1~20260613092250.77), Debian LLD 22.1.8

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/9a6fe2a54d0f/disk-fb28aa72.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/742b23a1d931/vmlinux-fb28aa72.xz
kernel image: https://storage.googleapis.com/syzbot-assets/b3f257c16d2e/bzImage-fb28aa72.xz

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

WARNING: CPU: 1 PID: 4772 at kernel/locking/rwsem.c:1345 __up_read+0x628/0x6b0 kernel/locking/rwsem.c:1345
Modules linked in:
CPU: 1 PID: 4772 Comm: syz.1.157 Not tainted syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/24/2026
RIP: 0010:__up_read+0x628/0x6b0 kernel/locking/rwsem.c:1345
Code: 0f 44 d0 48 c7 c7 20 0b 8c 8a 48 c7 c6 c0 0b 8c 8a 48 89 da 48 8b 4c 24 08 4d 89 e0 4d 89 f1 41 52 e8 cc 4f ea ff 48 83 c4 08 <0f> 0b 4c 8b 3c 24 e9 40 fb ff ff 48 c7 c1 a8 3f 21 8e 80 e1 07 80
RSP: 0018:ffffc900033478e0 EFLAGS: 00010292
RAX: 949236f6b8596300 RBX: 0000000000000000 RCX: 0000000000080000
RDX: ffffc9000eac2000 RSI: 0000000000008189 RDI: 000000000000818a
RBP: ffffc90003347990 R08: ffffc90003347567 R09: 1ffff92000668eac
R10: dffffc0000000000 R11: fffff52000668ead R12: 0000000000000000
R13: 1ffff92000668f20 R14: ffff88807f841e00 R15: ffff8880727d99a8
FS: 00007f5deba906c0(0000) GS:ffff8880b8f00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f990f96b000 CR3: 000000007c738000 CR4: 00000000003506e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
inode_unlock_shared include/linux/fs.h:773 [inline]
open_last_lookups fs/namei.c:3564 [inline]
path_openat+0x13b1/0x2f10 fs/namei.c:3788
do_filp_open+0x1ee/0x420 fs/namei.c:3818
do_sys_openat2+0x14b/0x4f0 fs/open.c:1320
do_sys_open fs/open.c:1336 [inline]
__do_sys_openat fs/open.c:1352 [inline]
__se_sys_openat fs/open.c:1347 [inline]
__x64_sys_openat+0x135/0x160 fs/open.c:1347
do_syscall_x64 arch/x86/entry/common.c:46 [inline]
do_syscall_64+0x4c/0xa0 arch/x86/entry/common.c:76
entry_SYSCALL_64_after_hwframe+0x68/0xd2
RIP: 0033:0x7f5deab9e019
Code: ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 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 e8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007f5deba90028 EFLAGS: 00000246 ORIG_RAX: 0000000000000101
RAX: ffffffffffffffda RBX: 00007f5deae26090 RCX: 00007f5deab9e019
RDX: 0000000000000000 RSI: 0000200000000400 RDI: ffffffffffffff9c
RBP: 00007f5deac3500c R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000081 R11: 0000000000000246 R12: 0000000000000000
R13: 00007f5deae26128 R14: 00007f5deae26090 R15: 00007fffce2eff98
</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
Reply all
Reply to author
Forward
0 new messages