Netdev List
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Zhiling Zou <zhilinz@nebusec.ai>
Cc: netdev@vger.kernel.org, dev@openvswitch.org, aconole@redhat.com,
	echaudro@redhat.com, i.maximets@ovn.org, davem@davemloft.net,
	edumazet@google.com, pabeni@redhat.com, horms@kernel.org,
	pshelar@nicira.com, tgraf@suug.ch, joestringer@nicira.com,
	vega@nebusec.ai
Subject: Re: [PATCH net 0/1] openvswitch: avoid reallocating confirmed conntrack labels
Date: Wed, 16 Sep 2026 01:10:06 +0000	[thread overview]
Message-ID: <178952100637.2346086.13652834104390120969.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <cover.1789218015.git.zhilinz@nebusec.ai>

Hello:

This patch was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:

On Sat, 12 Sep 2026 21:22:42 +0800 you wrote:
> Hi Linux kernel maintainers,
> 
> We found and validated an issue in net/openvswitch/conntrack.c. The bug
> is reachable by a root user through BPF and Open vSwitch netlink.
> We've tested it, and it should not affect any other functionality.
> 
> We will provide detailed information about the bug
> in this email, along with a PoC to trigger it.
> 
> [...]

Here is the summary with links:
  - [net,1/1] openvswitch: avoid reallocating confirmed conntrack labels
    https://git.kernel.org/netdev/net/c/3f118c8217c1

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      parent reply	other threads:[~2026-09-16  1:11 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-12 13:22 [PATCH net 0/1] openvswitch: avoid reallocating confirmed conntrack labels Zhiling Zou
2026-09-12 13:22 ` [PATCH net 1/1] " Zhiling Zou
2026-09-14 21:44   ` Ilya Maximets
2026-09-15 12:05   ` Aaron Conole
2026-09-16  1:10 ` 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=178952100637.2346086.13652834104390120969.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=horms@kernel.org \
    --cc=i.maximets@ovn.org \
    --cc=joestringer@nicira.com \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=pshelar@nicira.com \
    --cc=tgraf@suug.ch \
    --cc=vega@nebusec.ai \
    --cc=zhilinz@nebusec.ai \
    /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