From: patchwork-bot+netdevbpf@kernel.org
To: Aaron Conole <aconole@redhat.com>
Cc: netdev@vger.kernel.org, pshelar@ovn.org, kuba@kernel.org,
davem@davemloft.net, pabeni@redhat.com, edumazet@google.com,
tgraf@suug.ch, dev@openvswitch.org, echaudro@redhat.com,
i.maximets@ovn.org, wangchuanlei@inspur.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH net] net: openvswitch: release vport resources on failure
Date: Thu, 22 Dec 2022 01:50:16 +0000 [thread overview]
Message-ID: <167167381609.8581.3845194833780051366.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20221220212717.526780-1-aconole@redhat.com>
Hello:
This patch was applied to netdev/net.git (master)
by Jakub Kicinski <kuba@kernel.org>:
On Tue, 20 Dec 2022 16:27:17 -0500 you wrote:
> A recent commit introducing upcall packet accounting failed to properly
> release the vport object when the per-cpu stats struct couldn't be
> allocated. This can cause dangling pointers to dp objects long after
> they've been released.
>
> Cc: Eelco Chaudron <echaudro@redhat.com>
> Cc: wangchuanlei <wangchuanlei@inspur.com>
> Fixes: 1933ea365aa7 ("net: openvswitch: Add support to count upcall packets")
> Reported-by: syzbot+8f4e2dcfcb3209ac35f9@syzkaller.appspotmail.com
> Signed-off-by: Aaron Conole <aconole@redhat.com>
>
> [...]
Here is the summary with links:
- [net] net: openvswitch: release vport resources on failure
https://git.kernel.org/netdev/net/c/95637d91fefd
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:[~2022-12-22 1:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-20 21:27 [PATCH net] net: openvswitch: release vport resources on failure Aaron Conole
2022-12-21 9:48 ` Eelco Chaudron
2022-12-21 10:11 ` Michal Swiatkowski
2022-12-22 1: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=167167381609.8581.3845194833780051366.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=aconole@redhat.com \
--cc=davem@davemloft.net \
--cc=dev@openvswitch.org \
--cc=echaudro@redhat.com \
--cc=edumazet@google.com \
--cc=i.maximets@ovn.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=pshelar@ovn.org \
--cc=tgraf@suug.ch \
--cc=wangchuanlei@inspur.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.