From: syzbot <syzbot+4d29d76a0da7a8c4d86c@syzkaller.appspotmail.com>
To: davem@davemloft.net, dominique.martinet@cea.fr, ericvh@gmail.com,
jiangyiwen@huwei.com, linux-kernel@vger.kernel.org,
lucho@ionkov.net, netdev@vger.kernel.org, rminnich@sandia.gov,
syzkaller-bugs@googlegroups.com, tomasbortoli@gmail.com,
v9fs-developer@lists.sourceforge.net
Subject: Re: general protection fault in p9_conn_cancel
Date: Thu, 07 Nov 2019 05:42:04 -0800 [thread overview]
Message-ID: <000000000000b4731e0596c1d418@google.com> (raw)
In-Reply-To: <000000000000ee4dab0570be896c@google.com>
syzbot suspects this bug was fixed by commit:
commit 9f476d7c540cb57556d3cc7e78704e6cd5100f5f
Author: Tomas Bortoli <tomasbortoli@gmail.com>
Date: Mon Jul 23 18:42:53 2018 +0000
net/9p/trans_fd.c: fix race by holding the lock
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=1150b430600000
start commit: 30c2c32d Merge tag 'drm-fixes-2018-07-10' of git://anongit..
git tree: upstream
kernel config: https://syzkaller.appspot.com/x/.config?x=25856fac4e580aa7
dashboard link: https://syzkaller.appspot.com/bug?extid=4d29d76a0da7a8c4d86c
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=10e2c5b2400000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=179415b2400000
If the result looks correct, please mark the bug fixed by replying with:
#syz fix: net/9p/trans_fd.c: fix race by holding the lock
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
prev parent reply other threads:[~2019-11-07 13:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-11 19:49 general protection fault in p9_conn_cancel syzbot
2019-11-07 13:42 ` syzbot [this message]
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=000000000000b4731e0596c1d418@google.com \
--to=syzbot+4d29d76a0da7a8c4d86c@syzkaller.appspotmail.com \
--cc=davem@davemloft.net \
--cc=dominique.martinet@cea.fr \
--cc=ericvh@gmail.com \
--cc=jiangyiwen@huwei.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lucho@ionkov.net \
--cc=netdev@vger.kernel.org \
--cc=rminnich@sandia.gov \
--cc=syzkaller-bugs@googlegroups.com \
--cc=tomasbortoli@gmail.com \
--cc=v9fs-developer@lists.sourceforge.net \
/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;
as well as URLs for NNTP newsgroup(s).