From: syzbot <syzbot+2222c34dc40b515f30dc@syzkaller.appspotmail.com>
To: Dominique Martinet <asmadeus@codewreck.org>
Cc: asmadeus@codewreck.org, davem@davemloft.net, dvyukov@google.com,
ericvh@gmail.com, linux-kernel@vger.kernel.org, lucho@ionkov.net,
netdev@vger.kernel.org, rminnich@sandia.gov,
syzkaller-bugs@googlegroups.com,
v9fs-developer@lists.sourceforge.net
Subject: Re: Re: BUG: corrupted list in p9_read_work
Date: Wed, 10 Oct 2018 07:49:11 -0700 [thread overview]
Message-ID: <00000000000010889e0577e0f5f2@google.com> (raw)
In-Reply-To: <20181010144855.GB20918@nautica>
> Dmitry Vyukov wrote on Wed, Oct 10, 2018:
>> > Back to the current patch, since as I said I am not confident this is a
>> > good enough fix for the current bug, will I get notified if the bug
>> > happens again once the patch hits linux-next with the Reported-by tag ?
>> > (I don't have the setup necessary to run a syz repro as there is no C
>> > repro, and won't have much time to do that setup sorry)
>> Yes, the bug will be reported again if it still happens after the
>> patch is merged (not just into linux-next, but into all tested trees,
>> but it does not matter much). So marking bugs as fixed tentatively is
>> fine if that's our best guess.
> Ok, thanks for confirming...
>> But note that syzbot can test fixes itself on request. It boils down
>> to just giving it the patch and the base tree:
>> https://github.com/google/syzkaller/blob/master/docs/syzbot.md#testing-patches
> .. and for clarifying that bit, let's try that! :)
> #syz test: git://github.com/martinetd/linux
> e4ca13f7d075e551dc158df6af18fb412a1dba0a
"git://github.com/martinetd/linux" does not look like a valid git repo
address.
> --
> Dominique
next prev parent reply other threads:[~2018-10-10 14:49 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-16 5:59 BUG: corrupted list in p9_read_work syzbot
2018-10-09 1:07 ` syzbot
2018-10-09 2:09 ` Dominique Martinet
2018-10-09 4:05 ` [PATCH 1/2] 9p/trans_fd: abort p9_read_work if req status changed Dominique Martinet
2018-10-09 4:05 ` [PATCH 2/2] 9p/trans_fd: put worker reqs on destroy Dominique Martinet
2018-10-09 13:19 ` Tomas Bortoli
2018-10-15 10:46 ` Dominique Martinet
2018-10-10 14:03 ` BUG: corrupted list in p9_read_work Dmitry Vyukov
2018-10-10 14:40 ` Dominique Martinet
2018-10-10 14:51 ` Dmitry Vyukov
2018-10-10 15:58 ` Dominique Martinet
2018-10-11 12:33 ` Dmitry Vyukov
2018-10-11 13:10 ` Dominique Martinet
2018-10-11 13:27 ` Dmitry Vyukov
2018-10-11 13:40 ` Dmitry Vyukov
2018-10-11 14:28 ` 9p/RDMA for syzkaller (Was: BUG: corrupted list in p9_read_work) Dominique Martinet
2018-10-12 14:42 ` Dmitry Vyukov
2018-10-11 14:19 ` Dominique Martinet
2018-10-12 14:50 ` Dmitry Vyukov
2018-10-12 15:08 ` Dominique Martinet
2018-11-17 8:46 ` Dominique Martinet
2018-11-20 11:20 ` Dmitry Vyukov
2018-11-20 11:28 ` Dominique Martinet
2018-10-10 14:29 ` BUG: corrupted list in p9_read_work Dmitry Vyukov
2018-10-10 14:48 ` Dominique Martinet
2018-10-10 14:49 ` syzbot [this message]
2018-10-10 16:00 ` Dominique Martinet
2018-10-10 16:02 ` syzbot
2018-10-10 16:10 ` Dominique Martinet
2018-10-10 16:29 ` syzbot
2018-10-10 16:36 ` Dmitry Vyukov
2018-10-10 22:55 ` Dominique Martinet
2018-10-10 14:42 ` Dmitry Vyukov
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=00000000000010889e0577e0f5f2@google.com \
--to=syzbot+2222c34dc40b515f30dc@syzkaller.appspotmail.com \
--cc=asmadeus@codewreck.org \
--cc=davem@davemloft.net \
--cc=dvyukov@google.com \
--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=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 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.