From: syzbot <syzbot+be8872fcb764bf9fea73@syzkaller.appspotmail.com>
To: almaz.alexandrovich@paragon-software.com,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
ntfs3@lists.linux.dev, syzkaller-bugs@googlegroups.com,
viro@zeniv.linux.org.uk
Subject: Re: [syzbot] [vfs?] [ntfs3?] WARNING in path_openat
Date: Tue, 10 Jan 2023 23:15:41 -0800 [thread overview]
Message-ID: <0000000000009dfa9805f1f7c43f@google.com> (raw)
In-Reply-To: <000000000000a0d7f305eecfcbb9@google.com>
syzbot has found a reproducer for the following issue on:
HEAD commit: 40c18f363a08 Merge tag '6.2-rc3-ksmbd-server-fixes' of git..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=14a30e1c480000
kernel config: https://syzkaller.appspot.com/x/.config?x=ebc110f9741920ed
dashboard link: https://syzkaller.appspot.com/bug?extid=be8872fcb764bf9fea73
compiler: Debian clang version 13.0.1-++20220126092033+75e33f71c2da-1~exp1~20220126212112.63, GNU ld (GNU Binutils for Debian) 2.35.2
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=1505b0ce480000
Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/4b974f49dd49/disk-40c18f36.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/8d735ca0c438/vmlinux-40c18f36.xz
kernel image: https://storage.googleapis.com/syzbot-assets/6aeef3d597b4/bzImage-40c18f36.xz
mounted in repro: https://storage.googleapis.com/syzbot-assets/e9ddd28ad880/mount_0.gz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+be8872fcb764bf9fea73@syzkaller.appspotmail.com
DEBUG_RWSEMS_WARN_ON((rwsem_owner(sem) != current) && !rwsem_test_oflags(sem, RWSEM_NONSPINNABLE)): count = 0x0, magic = 0xffff88806a1ef1d0, owner = 0x0, curr 0xffff88802561ba80, list empty
WARNING: CPU: 1 PID: 10307 at kernel/locking/rwsem.c:1361 __up_write kernel/locking/rwsem.c:1360 [inline]
WARNING: CPU: 1 PID: 10307 at kernel/locking/rwsem.c:1361 up_write+0x4f9/0x580 kernel/locking/rwsem.c:1615
Modules linked in:
CPU: 1 PID: 10307 Comm: syz-executor.5 Not tainted 6.2.0-rc3-syzkaller-00014-g40c18f363a08 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/26/2022
RIP: 0010:__up_write kernel/locking/rwsem.c:1360 [inline]
RIP: 0010:up_write+0x4f9/0x580 kernel/locking/rwsem.c:1615
Code: c7 00 ad ed 8a 48 c7 c6 a0 af ed 8a 48 8b 54 24 28 48 8b 4c 24 18 4d 89 e0 4c 8b 4c 24 30 31 c0 53 e8 9b 59 e8 ff 48 83 c4 08 <0f> 0b e9 6b fd ff ff 48 c7 c1 98 a4 96 8e 80 e1 07 80 c1 03 38 c1
RSP: 0018:ffffc900053ef840 EFLAGS: 00010292
RAX: 7a73507bb1e00700 RBX: ffffffff8aedade0 RCX: ffff88802561ba80
RDX: 0000000000000000 RSI: 0000000080000000 RDI: 0000000000000000
RBP: ffffc900053ef910 R08: ffffffff816f2c9d R09: fffff52000a7dec1
R10: fffff52000a7dec1 R11: 1ffff92000a7dec0 R12: 0000000000000000
R13: ffff88806a1ef1d0 R14: 1ffff92000a7df10 R15: dffffc0000000000
FS: 00007fd23b092700(0000) GS:ffff8880b9900000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000555555ea4848 CR3: 000000001d10d000 CR4: 00000000003506e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
inode_unlock include/linux/fs.h:761 [inline]
open_last_lookups fs/namei.c:3485 [inline]
path_openat+0x14ff/0x2dd0 fs/namei.c:3711
do_filp_open+0x264/0x4f0 fs/namei.c:3741
do_sys_openat2+0x124/0x4e0 fs/open.c:1310
do_sys_open fs/open.c:1326 [inline]
__do_sys_openat fs/open.c:1342 [inline]
__se_sys_openat fs/open.c:1337 [inline]
__x64_sys_openat+0x243/0x290 fs/open.c:1337
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+0x63/0xcd
RIP: 0033:0x7fd23a28c0c9
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:00007fd23b092168 EFLAGS: 00000246 ORIG_RAX: 0000000000000101
RAX: ffffffffffffffda RBX: 00007fd23a3ac050 RCX: 00007fd23a28c0c9
RDX: 0000000000000240 RSI: 0000000020000000 RDI: ffffffffffffff9c
RBP: 00007fd23a2e7ae9 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007ffdfbd42a1f R14: 00007fd23b092300 R15: 0000000000022000
</TASK>
next prev parent reply other threads:[~2023-01-11 7:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-02 3:18 [syzbot] WARNING in path_openat syzbot
2023-01-11 7:15 ` syzbot [this message]
2023-01-26 23:55 ` [syzbot] [vfs?] [ntfs3?] " syzbot
2023-07-27 5:33 ` [syzbot] " syzbot
2023-07-27 6:47 ` Aleksandr Nogikh
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=0000000000009dfa9805f1f7c43f@google.com \
--to=syzbot+be8872fcb764bf9fea73@syzkaller.appspotmail.com \
--cc=almaz.alexandrovich@paragon-software.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ntfs3@lists.linux.dev \
--cc=syzkaller-bugs@googlegroups.com \
--cc=viro@zeniv.linux.org.uk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.