From: Parav Pandit <parav@nvidia•com>
To: <mst@redhat•com>, <jasowang@redhat•com>, <davem@davemloft•net>,
<kuba@kernel•org>, <netdev@vger•kernel.org>
Cc: <edumazet@google•com>, <pabeni@redhat•com>, <ast@kernel•org>,
<daniel@iogearbox•net>, <hawk@kernel•org>,
<virtualization@lists•linux-foundation.org>,
<bpf@vger•kernel.org>, "Parav Pandit" <parav@nvidia•com>
Subject: [PATCH 0/2] virtio-net: close() to follow mirror of open()
Date: Thu, 2 Feb 2023 07:00:36 +0200 [thread overview]
Message-ID: <20230202050038.3187-1-parav@nvidia.com> (raw)
Hi,
This two small patches improves ndo_close() callback to follow
the mirror sequence of ndo_open() callback. This improves the code auditing
and also ensure that xdp rxq info is not unregistered while NAPI on
RXQ is ongoing.
Please review.
Patch summary:
patch-1 ensures that xdp rq info is unregistered after rq napi is disabled
patch-2 keeps the mirror sequence for close() be mirror of open()
Parav Pandit (2):
virtio-net: Keep stop() to follow mirror sequence of open()
virtio-net: Maintain reverse cleanup order
drivers/net/virtio_net.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
--
2.26.2
next reply other threads:[~2023-02-02 5:01 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-02 5:00 Parav Pandit [this message]
2023-02-02 5:00 ` [PATCH 1/2] virtio-net: Keep stop() to follow mirror sequence of open() Parav Pandit
2023-02-02 12:23 ` Jiri Pirko
2023-02-02 5:00 ` [PATCH 2/2] virtio-net: Maintain reverse cleanup order Parav Pandit
2023-02-02 12:26 ` Jiri Pirko
2023-02-02 15:10 ` Parav Pandit
2023-02-02 15:46 ` Jiri Pirko
2023-02-02 16:33 ` Parav Pandit
2023-02-02 10:56 ` [PATCH 0/2] virtio-net: close() to follow mirror of open() Michael S. Tsirkin
2023-02-02 18:40 ` patchwork-bot+netdevbpf
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=20230202050038.3187-1-parav@nvidia.com \
--to=parav@nvidia$(echo .)com \
--cc=ast@kernel$(echo .)org \
--cc=bpf@vger$(echo .)kernel.org \
--cc=daniel@iogearbox$(echo .)net \
--cc=davem@davemloft$(echo .)net \
--cc=edumazet@google$(echo .)com \
--cc=hawk@kernel$(echo .)org \
--cc=jasowang@redhat$(echo .)com \
--cc=kuba@kernel$(echo .)org \
--cc=mst@redhat$(echo .)com \
--cc=netdev@vger$(echo .)kernel.org \
--cc=pabeni@redhat$(echo .)com \
--cc=virtualization@lists$(echo .)linux-foundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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