From: Dominique Martinet <asmadeus@codewreck.org>
To: Tomas Bortoli <tomasbortoli@gmail.com>
Cc: v9fs-developer@lists.sourceforge.net, syzkaller@googlegroups.com,
davem@davemloft.net, linux-kernel@vger.kernel.org,
netdev@vger.kernel.org
Subject: Re: [V9fs-developer] [PATCH] 9p: fix Use-After-Free in p9_write_work()
Date: Mon, 30 Jul 2018 02:18:00 +0200 [thread overview]
Message-ID: <20180730001800.GA5960@nautica> (raw)
In-Reply-To: <20180729233336.GB28684@nautica>
Dominique Martinet wrote on Mon, Jul 30, 2018:
> Basically, a more global view of the problem is a race between
> p9_tag_lookup returning a p9_req_t and another thread freeing it.
(just correcting myself here, p9_tag_lookup won't be enough for the
write side, but similarily you'd just need to increment the refcount
when you schedule work with it and decrement when the worker is done)
--
Dominique
next prev parent reply other threads:[~2018-07-30 0:18 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 ` Dominique Martinet [this message]
2018-07-30 5:54 ` Dmitry Vyukov
2018-07-30 6:00 ` Dominique Martinet
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=20180730001800.GA5960@nautica \
--to=asmadeus@codewreck.org \
--cc=davem@davemloft.net \
--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