[v5.15] WARNING in iterate_dir

0 views
Skip to first unread message

syzbot

unread,
Sep 27, 2023, 11:25:42 AM9/27/23
to syzkaller...@googlegroups.com
Hello,

syzbot found the following issue on:

HEAD commit: b911329317b4 Linux 5.15.133
git tree: linux-5.15.y
console output: https://syzkaller.appspot.com/x/log.txt?x=1056f832680000
kernel config: https://syzkaller.appspot.com/x/.config?x=a9c9f0083f439f72
dashboard link: https://syzkaller.appspot.com/bug?extid=127caeb33a6ad5883a5a
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/46530025981a/disk-b9113293.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/d27830145a50/vmlinux-b9113293.xz
kernel image: https://storage.googleapis.com/syzbot-assets/ee1d0b88a1d9/bzImage-b9113293.xz

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

------------[ cut here ]------------
DEBUG_RWSEMS_WARN_ON(!is_rwsem_reader_owned(sem)): count = 0x0, magic = 0xffff888029fd71d0, owner = 0x0, curr 0xffff8880785e3b80, list empty
WARNING: CPU: 0 PID: 5944 at kernel/locking/rwsem.c:1315 __up_read+0x5fe/0x690 kernel/locking/rwsem.c:1315
Modules linked in:
CPU: 0 PID: 5944 Comm: syz-executor.2 Not tainted 5.15.133-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 09/06/2023
RIP: 0010:__up_read+0x5fe/0x690 kernel/locking/rwsem.c:1315
Code: 8b 8a 48 0f 44 c1 48 c7 c7 e0 ff 8a 8a 48 c7 c6 80 00 8b 8a 4c 89 fa 4c 89 f1 49 89 d8 4d 89 e9 50 e8 46 19 ea ff 48 83 c4 08 <0f> 0b 48 bb 00 00 00 00 00 fc ff df 4c 8b 2c 24 e9 4e fb ff ff 48
RSP: 0018:ffffc900055e7cc0 EFLAGS: 00010296
RAX: c4a3c40937e81700 RBX: 0000000000000000 RCX: 0000000000040000
RDX: ffffc90003493000 RSI: 0000000000009908 RDI: 0000000000009909
RBP: ffffc900055e7d68 R08: ffffffff816658bc R09: ffffed10173467a8
R10: 0000000000000000 R11: dffffc0000000001 R12: ffff888029fd7228
R13: ffff8880785e3b80 R14: ffff888029fd71d0 R15: 0000000000000000
FS: 00007f8aeb8496c0(0000) GS:ffff8880b9b00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 000000002018e000 CR3: 00000000239a9000 CR4: 00000000003506e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
inode_unlock_shared include/linux/fs.h:802 [inline]
iterate_dir+0x4b2/0x570 fs/readdir.c:73
__do_sys_getdents fs/readdir.c:286 [inline]
__se_sys_getdents+0x1e8/0x4c0 fs/readdir.c:271
do_syscall_x64 arch/x86/entry/common.c:50 [inline]
do_syscall_64+0x3d/0xb0 arch/x86/entry/common.c:80
entry_SYSCALL_64_after_hwframe+0x61/0xcb
RIP: 0033:0x7f8af54e8ae9
Code: 28 00 00 00 75 05 48 83 c4 28 c3 e8 e1 20 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 b0 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007f8aeb8490c8 EFLAGS: 00000246 ORIG_RAX: 000000000000004e
RAX: ffffffffffffffda RBX: 00007f8af5608050 RCX: 00007f8af54e8ae9
RDX: 0000000000000040 RSI: 0000000020000580 RDI: 0000000000000004
RBP: 00007f8af553447a R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 000000000000006e R14: 00007f8af5608050 R15: 00007ffd05789038
</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 bug is already fixed, let syzbot know by replying with:
#syz fix: exact-commit-title

If you want to overwrite bug's subsystems, reply with:
#syz set subsystems: new-subsystem
(See the list of subsystem names on the web dashboard)

If the bug is a duplicate of another bug, reply with:
#syz dup: exact-subject-of-another-report

If you want to undo deduplication, reply with:
#syz undup

syzbot

unread,
Jan 5, 2024, 10:25:15 AMJan 5
to syzkaller...@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