From: "Michael S. Tsirkin" <mst@redhat.com>
To: Hillf Danton <hdanton@sina.com>
Cc: Nikolay Kuratov <kniv@yandex-team.ru>,
linux-kernel@vger.kernel.org, virtualization@lists.linux.dev,
Jason Wang <jasowang@redhat.com>,
Eugenio Perez <eperezma@redhat.com>,
Lei Yang <leiyang@redhat.com>,
Andrey Ryabinin <arbn@yandex-team.com>,
Andrey Smetanin <asmetanin@yandex-team.ru>
Subject: Re: [PATCH v2] vhost/net: Replace wait_queue with completion in ubufs reference
Date: Sun, 20 Jul 2025 12:13:10 -0400 [thread overview]
Message-ID: <20250720121256-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <20250718230356.2459-1-hdanton@sina.com>
On Sat, Jul 19, 2025 at 07:03:23AM +0800, Hillf Danton wrote:
> On Fri, 18 Jul 2025 14:03:55 +0300 Nikolay Kuratov wrote:
> > When operating on struct vhost_net_ubuf_ref, the following execution
> > sequence is theoretically possible:
> > CPU0 is finalizing DMA operation CPU1 is doing VHOST_NET_SET_BACKEND
> > // &ubufs->refcount == 2
> > vhost_net_ubuf_put() vhost_net_ubuf_put_wait_and_free(oldubufs)
> > vhost_net_ubuf_put_and_wait()
> > vhost_net_ubuf_put()
> > int r = atomic_sub_return(1, &ubufs->refcount);
> > // r = 1
> > int r = atomic_sub_return(1, &ubufs->refcount);
> > // r = 0
> > wait_event(ubufs->wait, !atomic_read(&ubufs->refcount));
> > // no wait occurs here because condition is already true
> > kfree(ubufs);
> > if (unlikely(!r))
> > wake_up(&ubufs->wait); // use-after-free
> >
> > This leads to use-after-free on ubufs access. This happens because CPU1
> > skips waiting for wake_up() when refcount is already zero.
> >
> > To prevent that use a completion instead of wait_queue as the ubufs
> > notification mechanism. wait_for_completion() guarantees that there will
> > be complete() call prior to its return.
> >
> Alternatively rcu helps.
>
> --- x/drivers/vhost/net.c
> +++ y/drivers/vhost/net.c
> @@ -96,6 +96,7 @@ struct vhost_net_ubuf_ref {
> atomic_t refcount;
> wait_queue_head_t wait;
> struct vhost_virtqueue *vq;
> + struct rcu_head rcu;
> };
>
> #define VHOST_NET_BATCH 64
> @@ -247,9 +248,13 @@ vhost_net_ubuf_alloc(struct vhost_virtqu
>
> static int vhost_net_ubuf_put(struct vhost_net_ubuf_ref *ubufs)
> {
> - int r = atomic_sub_return(1, &ubufs->refcount);
> + int r;
> +
> + rcu_read_lock();
> + r = atomic_sub_return(1, &ubufs->refcount);
> if (unlikely(!r))
> wake_up(&ubufs->wait);
> + rcu_read_unlock();
> return r;
> }
>
> @@ -262,7 +267,7 @@ static void vhost_net_ubuf_put_and_wait(
> static void vhost_net_ubuf_put_wait_and_free(struct vhost_net_ubuf_ref *ubufs)
> {
> vhost_net_ubuf_put_and_wait(ubufs);
> - kfree(ubufs);
> + kfree_rcu(ubufs, rcu);
> }
>
> static void vhost_net_clear_ubuf_info(struct vhost_net *n)
I like that.
--
MST
next prev parent reply other threads:[~2025-07-20 16:13 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-18 11:03 [PATCH v2] vhost/net: Replace wait_queue with completion in ubufs reference Nikolay Kuratov
2025-07-18 12:46 ` Hillf Danton
2025-07-18 13:24 ` [PATCH] " Nikolay Kuratov
2025-07-18 22:11 ` Hillf Danton
2025-07-18 23:03 ` [PATCH v2] " Hillf Danton
2025-07-20 16:13 ` Michael S. Tsirkin [this message]
2025-07-21 14:52 ` Lei Yang
2025-08-05 10:02 ` Michael S. Tsirkin
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=20250720121256-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=arbn@yandex-team.com \
--cc=asmetanin@yandex-team.ru \
--cc=eperezma@redhat.com \
--cc=hdanton@sina.com \
--cc=jasowang@redhat.com \
--cc=kniv@yandex-team.ru \
--cc=leiyang@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=virtualization@lists.linux.dev \
/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.