From: patchwork-bot+netdevbpf@kernel.org
To: Feng Liu <feliu@nvidia.com>
Cc: virtualization@lists.linux-foundation.org,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
bpf@vger.kernel.org, jasowang@redhat.com, mst@redhat.com,
xuanzhuo@linux.alibaba.com, simon.horman@corigine.com,
bodong@nvidia.com, jiri@nvidia.com, witu@nvidia.com
Subject: Re: [PATCH net v6] virtio_net: Fix error unwinding of XDP initialization
Date: Mon, 15 May 2023 07:50:19 +0000 [thread overview]
Message-ID: <168413701978.26935.8394779439623011528.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230512151812.1806-1-feliu@nvidia.com>
Hello:
This patch was applied to netdev/net.git (main)
by David S. Miller <davem@davemloft.net>:
On Fri, 12 May 2023 11:18:12 -0400 you wrote:
> When initializing XDP in virtnet_open(), some rq xdp initialization
> may hit an error causing net device open failed. However, previous
> rqs have already initialized XDP and enabled NAPI, which is not the
> expected behavior. Need to roll back the previous rq initialization
> to avoid leaks in error unwinding of init code.
>
> Also extract helper functions of disable and enable queue pairs.
> Use newly introduced disable helper function in error unwinding and
> virtnet_close. Use enable helper function in virtnet_open.
>
> [...]
Here is the summary with links:
- [net,v6] virtio_net: Fix error unwinding of XDP initialization
https://git.kernel.org/netdev/net/c/5306623a9826
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2023-05-15 7:50 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-12 15:18 [PATCH net v6] virtio_net: Fix error unwinding of XDP initialization Feng Liu
2023-05-12 15:18 ` Feng Liu via Virtualization
2023-05-12 16:37 ` Michael S. Tsirkin
2023-05-12 16:37 ` Michael S. Tsirkin
2023-05-15 1:06 ` Jason Wang
2023-05-15 1:06 ` Jason Wang
2023-05-15 1:40 ` Xuan Zhuo
2023-05-15 1:40 ` Xuan Zhuo
2023-05-15 4:45 ` Michael S. Tsirkin
2023-05-15 4:45 ` Michael S. Tsirkin
2023-05-15 7:50 ` patchwork-bot+netdevbpf [this message]
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=168413701978.26935.8394779439623011528.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=bodong@nvidia.com \
--cc=bpf@vger.kernel.org \
--cc=feliu@nvidia.com \
--cc=jasowang@redhat.com \
--cc=jiri@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mst@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=simon.horman@corigine.com \
--cc=virtualization@lists.linux-foundation.org \
--cc=witu@nvidia.com \
--cc=xuanzhuo@linux.alibaba.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 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.