From: Michal Swiatkowski <michal.swiatkowski@linux.intel.com>
To: Zheng Wang <zyytlz.wz@163.com>
Cc: ericvh@gmail.com, lucho@ionkov.net, asmadeus@codewreck.org,
linux_oss@crudebyte.com, davem@davemloft.net,
edumazet@google.com, kuba@kernel.org, pabeni@redhat.com,
v9fs-developer@lists.sourceforge.net, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, hackerzheng666@gmail.com,
1395428693sheep@gmail.com, alex000young@gmail.com
Subject: Re: [PATCH net v3] 9p/xen : Fix use after free bug in xen_9pfs_front_remove due to race condition
Date: Mon, 13 Mar 2023 15:53:20 +0100 [thread overview]
Message-ID: <ZA844NfrYjj+lHy7@localhost.localdomain> (raw)
In-Reply-To: <20230313144325.3622082-1-zyytlz.wz@163.com>
On Mon, Mar 13, 2023 at 10:43:25PM +0800, Zheng Wang wrote:
> In xen_9pfs_front_probe, it calls xen_9pfs_front_alloc_dataring
> to init priv->rings and bound &ring->work with p9_xen_response.
>
> When it calls xen_9pfs_front_event_handler to handle IRQ requests,
> it will finally call schedule_work to start the work.
>
> When we call xen_9pfs_front_remove to remove the driver, there
> may be a sequence as follows:
>
> Fix it by finishing the work before cleanup in xen_9pfs_front_free.
>
> Note that, this bug is found by static analysis, which might be
> false positive.
>
> CPU0 CPU1
>
> |p9_xen_response
> xen_9pfs_front_remove|
> xen_9pfs_front_free|
> kfree(priv) |
> //free priv |
> |p9_tag_lookup
> |//use priv->client
>
> Fixes: 71ebd71921e4 ("xen/9pfs: connect to the backend")
> Signed-off-by: Zheng Wang <zyytlz.wz@163.com>
> ---
> v3:
> - remove unnecessary comment and move definition to the
> for loop suggested by Michal Swiatkowski
>
> v2:
> - fix type error of ring found by kernel test robot
> ---
> net/9p/trans_xen.c | 4 ++++
> 1 file changed, 4 insertions(+)
>
[...]
Thanks for changes
Reviewed-by: Michal Swiatkowski <michal.swiatkowski@linux.intel.com>
next prev parent reply other threads:[~2023-03-13 14:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-13 14:43 [PATCH net v3] 9p/xen : Fix use after free bug in xen_9pfs_front_remove due to race condition Zheng Wang
2023-03-13 14:53 ` Michal Swiatkowski [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-03-13 16:59 Zheng Wang
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=ZA844NfrYjj+lHy7@localhost.localdomain \
--to=michal.swiatkowski@linux.intel.com \
--cc=1395428693sheep@gmail.com \
--cc=alex000young@gmail.com \
--cc=asmadeus@codewreck.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=ericvh@gmail.com \
--cc=hackerzheng666@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux_oss@crudebyte.com \
--cc=lucho@ionkov.net \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=v9fs-developer@lists.sourceforge.net \
--cc=zyytlz.wz@163.com \
/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