From: Jason Wang <jasowang@redhat.com>
To: "Eugenio Pérez" <eperezma@redhat.com>
Cc: qemu-devel@nongnu.org, dtatulea@nvidia.com, mcoqueli@redhat.com,
mst@redhat.com, si-wei.liu@oracle.com, qemu-stable@nongnu.org,
leiyang@redhat.com, Ani Sinha <anisinha@redhat.com>
Subject: Re: [PATCH v2 2/2] net: move backend cleanup to NIC cleanup
Date: Wed, 23 Oct 2024 12:04:17 +0800 [thread overview]
Message-ID: <CACGkMEviROuas_MT-tT+PMw0PCJa9Ossu1a-oKHpgt_TAiZxhg@mail.gmail.com> (raw)
In-Reply-To: <20240912165408.234447-3-eperezma@redhat.com>
On Fri, Sep 13, 2024 at 12:54 AM Eugenio Pérez <eperezma@redhat.com> wrote:
>
> Commit a0d7215e33 ("vhost-vdpa: do not cleanup the vdpa/vhost-net
> structures if peer nic is present") effectively delayed the backend
> cleanup, allowing the frontend or the guest to access it resources as
> long as the frontend is still visible to the guest.
>
> However it does not clean up the resources until the qemu process is
> over. This causes an effective leak if the device is deleted with
> device_del, as there is no way to close the vdpa device. This makes
> impossible to re-add that device to this or other QEMU instances until
> the first instance of QEMU is finished.
>
> Move the cleanup from qemu_cleanup to the NIC deletion and to
> net_cleanup.
>
> Fixes: a0d7215e33 ("vhost-vdpa: do not cleanup the vdpa/vhost-net structures if peer nic is present")
> Reported-by: Lei Yang <leiyang@redhat.com>
> Signed-off-by: Eugenio Pérez <eperezma@redhat.com>
> ---
> v2: Remove NIC peer also at net_cleanup. vhost-user trust all the
> backends are clean before qemu removes char devices.
>
> This is not a requisite introduced by this commit as
> system/runstate.c:qemu_cleanup shows.
> ---
Unfortunately, this fails the build:
https://gitlab.com/jasowang/qemu/-/jobs/8138832559
Thanks
next prev parent reply other threads:[~2024-10-23 4:05 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-12 16:54 [PATCH v2 0/2] Move net backend cleanup to NIC cleanup Eugenio Pérez
2024-09-12 16:54 ` [PATCH v2 1/2] net: parameterize the removing client from nc list Eugenio Pérez
2024-09-12 16:54 ` [PATCH v2 2/2] net: move backend cleanup to NIC cleanup Eugenio Pérez
2024-09-18 3:57 ` Si-Wei Liu
2024-10-09 8:34 ` Jason Wang
2024-10-23 4:04 ` Jason Wang [this message]
2024-12-20 21:01 ` [PATCH v2 0/2] Move net " Michael Tokarev
2024-12-23 16:33 ` Eugenio Perez Martin
2025-01-06 16:03 ` Jonah Palmer
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=CACGkMEviROuas_MT-tT+PMw0PCJa9Ossu1a-oKHpgt_TAiZxhg@mail.gmail.com \
--to=jasowang@redhat.com \
--cc=anisinha@redhat.com \
--cc=dtatulea@nvidia.com \
--cc=eperezma@redhat.com \
--cc=leiyang@redhat.com \
--cc=mcoqueli@redhat.com \
--cc=mst@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-stable@nongnu.org \
--cc=si-wei.liu@oracle.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;
as well as URLs for NNTP newsgroup(s).