From: syzbot <syzbot+1788bd5d4e051da6ec08@syzkaller.appspotmail.com>
To: asmadeus@codewreck.org, davem@davemloft.net,
dominique.martinet@cea.fr, ericvh@gmail.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: BUG: corrupted list in p9_write_work
Date: Thu, 07 Nov 2019 05:42:05 -0800 [thread overview]
Message-ID: <000000000000bfa1ab0596c1d403@google.com> (raw)
In-Reply-To: <0000000000002a2fdf0573107004@google.com>
syzbot suspects this bug was fixed by commit:
commit 728356dedeff8ef999cb436c71333ef4ac51a81c
Author: Tomas Bortoli <tomasbortoli@gmail.com>
Date: Tue Aug 14 17:43:42 2018 +0000
9p: Add refcount to p9_req_t
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=10f2258a600000
start commit: 050cdc6c Merge git://git.kernel.org/pub/scm/linux/kernel/g..
git tree: upstream
kernel config: https://syzkaller.appspot.com/x/.config?x=49927b422dcf0b29
dashboard link: https://syzkaller.appspot.com/bug?extid=1788bd5d4e051da6ec08
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=1196b7ba400000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=1022391e400000
If the result looks correct, please mark the bug fixed by replying with:
#syz fix: 9p: Add refcount to p9_req_t
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: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-10 8:22 BUG: corrupted list in p9_write_work syzbot
2018-08-28 4:42 ` 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=000000000000bfa1ab0596c1d403@google.com \
--to=syzbot+1788bd5d4e051da6ec08@syzkaller.appspotmail.com \
--cc=asmadeus@codewreck.org \
--cc=davem@davemloft.net \
--cc=dominique.martinet@cea.fr \
--cc=ericvh@gmail.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).