From: syzbot <syzbot+a9c0867e4d1dd0c7ab19@syzkaller.appspotmail.com>
To: amir73il@gmail.com, asmadeus@codewreck.org, brauner@kernel.org,
corbet@lwn.net, eadavis@qq.com, ericvh@kernel.org,
jack@suse.com, jack@suse.cz, linux-doc@vger.kernel.org,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
linux_oss@crudebyte.com, lucho@ionkov.net, mjguzik@gmail.com,
syzkaller-bugs@googlegroups.com, v9fs@lists.linux.dev,
viro@zeniv.linux.org.uk, willy@infradead.org
Subject: Re: [syzbot] [udf?] general protection fault in d_splice_alias
Date: Thu, 06 Mar 2025 01:04:03 -0800 [thread overview]
Message-ID: <67c96503.050a0220.15b4b9.0030.GAE@google.com> (raw)
In-Reply-To: <67a11d8a.050a0220.163cdc.0051.GAE@google.com>
syzbot suspects this issue was fixed by commit:
commit 902e09c8acde117b00369521f54df817a983d4ab
Author: Al Viro <viro@zeniv.linux.org.uk>
Date: Mon Feb 3 21:16:09 2025 +0000
fix braino in "9p: fix ->rename_sem exclusion"
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=11d77078580000
start commit: 69e858e0b8b2 Merge tag 'uml-for-linus-6.14-rc1' of git://g..
git tree: upstream
kernel config: https://syzkaller.appspot.com/x/.config?x=d1a6d4df5fcc342f
dashboard link: https://syzkaller.appspot.com/bug?extid=a9c0867e4d1dd0c7ab19
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=125d0eb0580000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=13a595f8580000
If the result looks correct, please mark the issue as fixed by replying with:
#syz fix: fix braino in "9p: fix ->rename_sem exclusion"
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2025-03-06 9:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-03 19:48 [syzbot] [udf?] general protection fault in d_splice_alias syzbot
2025-03-06 9:04 ` syzbot [this message]
2025-03-06 21:12 ` Jan Kara
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=67c96503.050a0220.15b4b9.0030.GAE@google.com \
--to=syzbot+a9c0867e4d1dd0c7ab19@syzkaller.appspotmail.com \
--cc=amir73il@gmail.com \
--cc=asmadeus@codewreck.org \
--cc=brauner@kernel.org \
--cc=corbet@lwn.net \
--cc=eadavis@qq.com \
--cc=ericvh@kernel.org \
--cc=jack@suse.com \
--cc=jack@suse.cz \
--cc=linux-doc@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux_oss@crudebyte.com \
--cc=lucho@ionkov.net \
--cc=mjguzik@gmail.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=v9fs@lists.linux.dev \
--cc=viro@zeniv.linux.org.uk \
--cc=willy@infradead.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox