From: Dominique Martinet <asmadeus@codewreck.org>
To: Dmitry Vyukov <dvyukov@google.com>
Cc: Tomas Bortoli <tomasbortoli@gmail.com>,
David Miller <davem@davemloft.net>,
v9fs-developer@lists.sourceforge.net,
netdev <netdev@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
syzkaller <syzkaller@googlegroups.com>
Subject: Re: [PATCH] 9p: fix Use-After-Free in p9_write_work()
Date: Mon, 30 Jul 2018 08:00:21 +0200 [thread overview]
Message-ID: <20180730060021.GA22926@nautica> (raw)
In-Reply-To: <CACT4Y+bf1NfCV9aTRCR_qwA0jWxhYDkR3CS8jQcJyvkYXCming@mail.gmail.com>
Dmitry Vyukov wrote on Mon, Jul 30, 2018:
> On Mon, Jul 30, 2018 at 1:33 AM, Dominique Martinet
> <asmadeus@codewreck.org> wrote:
> > Tomas Bortoli wrote on Sun, Jul 29, 2018:
> >> There is a race condition between p9_free_req() and p9_write_work().
> >> A request might still need to be processed while p9_free_req() is called.
> >>
> >> To fix it, flush the read/write work before freeing any request.
> >>
> >> Signed-off-by: Tomas Bortoli <tomasbortoli@gmail.com>
> >> Reported-by: syzbot+467050c1ce275af2a5b8@syzkaller.appspotmail.com
> >
> > It looks like I have not received this report, I found it through google
> > in the lkml archives
>
> But you should have been received it? Or not?
> We had some complaints that syzbot emails were not delivered, but in
> these cases they were not delivered to lkml, and only to explicitly
> CCed people.
I'm not on lkml and the archives I found do not list who were Cc'd that
I can see - it might have tried to send a copy to v9fs-developer that is
held up in the moderation queue for all I know :/
I'm not complaining I didn't get a copy (if I ever find time to work on
these, I can work through the list on the website) - I just need to know
how to find the report corresponding to patchs being sent.
> > but Dmitry do you have a convenient-ish way of
> > finding the report on the syzkaller website with that reported-by tag?
>
> Well, you can do:
> http://syzkaller.appspot.com/bug?extid=467050c1ce275af2a5b8
Thanks, for some reason I only thought of bug?id= which didn't work,
this is perfect.
Cheers,
--
Dominique
next prev parent reply other threads:[~2018-07-30 6:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-29 13:02 [PATCH] 9p: fix Use-After-Free in p9_write_work() Tomas Bortoli
2018-07-29 23:33 ` Dominique Martinet
2018-07-30 0:18 ` [V9fs-developer] " Dominique Martinet
2018-07-30 5:54 ` Dmitry Vyukov
2018-07-30 6:00 ` Dominique Martinet [this message]
2018-07-30 9:45 ` Tomas Bortoli
2018-07-30 10:23 ` Dominique Martinet
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=20180730060021.GA22926@nautica \
--to=asmadeus@codewreck.org \
--cc=davem@davemloft.net \
--cc=dvyukov@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=syzkaller@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