From: Maxime Coquelin <maxime.coquelin@redhat.com>
To: Tiwei Bie <tiwei.bie@intel.com>, dev@dpdk.org, zhihong.wang@intel.com
Cc: stephen@networkplumber.org, stable@dpdk.org
Subject: Re: [dpdk-dev] [PATCH 20.02 v2] net/virtio-user: do not close tap when disabling queue pairs
Date: Tue, 14 Jan 2020 10:16:29 +0100 [thread overview]
Message-ID: <c6b6ea91-0140-efd7-9dd6-30bd8de484be@redhat.com> (raw)
In-Reply-To: <20191125081440.136906-1-tiwei.bie@intel.com>
On 11/25/19 9:14 AM, Tiwei Bie wrote:
> Do not close the tap fds when disabling queue pairs, instead,
> we just need to unbind the backend. Otherwise, tap port can be
> destroyed unexpectedly.
>
> Fixes: e3b434818bbb ("net/virtio-user: support kernel vhost")
> Cc: stable@dpdk.org
>
> Reported-by: Stephen Hemminger <stephen@networkplumber.org>
> Signed-off-by: Tiwei Bie <tiwei.bie@intel.com>
> ---
> v2:
> - Squash attach_queue/detach_queue into one routine (Stephen);
> - Use initializer instead of memset (Stephen);
> - Drop the cast to void * (Stephen);
>
> drivers/net/virtio/virtio_user/vhost_kernel.c | 34 +++++++++++++++----
> .../net/virtio/virtio_user/vhost_kernel_tap.c | 34 ++++++++++++-------
> .../net/virtio/virtio_user/vhost_kernel_tap.h | 8 +++++
> drivers/net/virtio/virtio_user/vhost_user.c | 4 +++
> .../net/virtio/virtio_user/virtio_user_dev.c | 5 ++-
> .../net/virtio/virtio_user/virtio_user_dev.h | 1 +
> 6 files changed, 65 insertions(+), 21 deletions(-)
>
Reviewed-by: Maxime Coquelin <maxime.coquelin@redhat.com>
Thanks,
Maxime
next prev parent reply other threads:[~2020-01-14 9:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-19 6:29 [dpdk-dev] [PATCH 20.02] " Tiwei Bie
2019-11-19 16:36 ` Stephen Hemminger
2019-11-20 2:46 ` Tiwei Bie
2019-11-25 8:14 ` [dpdk-dev] [PATCH 20.02 v2] " Tiwei Bie
2020-01-14 9:16 ` Maxime Coquelin [this message]
2020-01-15 11:18 ` Maxime Coquelin
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=c6b6ea91-0140-efd7-9dd6-30bd8de484be@redhat.com \
--to=maxime.coquelin@redhat.com \
--cc=dev@dpdk.org \
--cc=stable@dpdk.org \
--cc=stephen@networkplumber.org \
--cc=tiwei.bie@intel.com \
--cc=zhihong.wang@intel.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).