public inbox for netdev@vger.kernel.org
 help / color / mirror / Atom feed
From: Jakub Kicinski <kuba@kernel.org>
To: Antonio Quartulli <antonio@openvpn.net>
Cc: netdev@vger.kernel.org, ralf@mandelbit.com,
	Sabrina Dubroca <sd@queasysnail.net>,
	Paolo Abeni <pabeni@redhat.com>,
	Andrew Lunn <andrew+netdev@lunn.ch>,
	"David S. Miller" <davem@davemloft.net>,
	Eric Dumazet <edumazet@google.com>
Subject: Re: [PATCH net-next 0/9] pull request: ovpn 2026-03-17
Date: Thu, 19 Mar 2026 12:44:32 -0700	[thread overview]
Message-ID: <20260319124432.2fda076a@kernel.org> (raw)
In-Reply-To: <20260317104023.192548-1-antonio@openvpn.net>

On Tue, 17 Mar 2026 11:40:14 +0100 Antonio Quartulli wrote:
> This is (yet..yet..yet) another resend of the original PR meant for
> net-next.
> We have fixed the hitchups in the commit messages, as pointed out by the
> AI.
> 
> 
> This batch includes the following changes:
> * use correct constant when declaring nlattr array in ovpn_nl_key_swap_doit
> * use bitops.h API when possible
> * send netlink notification in case of client float event
> * implement support for asymmetric peer IDs
> * consolidate memory allocations during crypto operations
> * add netlink notification check in selftests
> * add asymmetric peer IDs check in selftest
> * add FW mark check in selftest

In addition to the mark test failing always three more tests hang
around 30% of the time on debug kernels:

https://netdev.bots.linux.dev/flakes.html?tn-needle=net-ovpn&min-flip=12

Please follow up with the fixes? More info how our CI builds the
kernels etc:
https://github.com/linux-netdev/nipa/wiki/How-to-run-netdev-selftests-CI-style

  parent reply	other threads:[~2026-03-19 19:44 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-17 10:40 [PATCH net-next 0/9] pull request: ovpn 2026-03-17 Antonio Quartulli
2026-03-17 10:40 ` [PATCH net-next 1/9] selftests: ovpn: allow compiling ovpn-cli.c with mbedtls3 Antonio Quartulli
2026-03-19 12:00   ` patchwork-bot+netdevbpf
2026-03-17 10:40 ` [PATCH net-next 2/9] ovpn: use correct array size to parse nested attributes in ovpn_nl_key_swap_doit Antonio Quartulli
2026-03-17 10:40 ` [PATCH net-next 3/9] ovpn: pktid: use bitops.h API Antonio Quartulli
2026-03-17 10:40 ` [PATCH net-next 4/9] ovpn: notify userspace on client float event Antonio Quartulli
2026-03-17 10:40 ` [PATCH net-next 5/9] selftests: ovpn: add notification parsing and matching Antonio Quartulli
2026-03-17 10:40 ` [PATCH net-next 6/9] ovpn: add support for asymmetric peer IDs Antonio Quartulli
2026-03-17 10:40 ` [PATCH net-next 7/9] selftests: ovpn: check asymmetric peer-id Antonio Quartulli
2026-03-17 10:40 ` [PATCH net-next 8/9] selftests: ovpn: add test for the FW mark feature Antonio Quartulli
2026-03-19 19:41   ` Jakub Kicinski
2026-03-17 10:40 ` [PATCH net-next 9/9] ovpn: consolidate crypto allocations in one chunk Antonio Quartulli
2026-03-19 19:44 ` Jakub Kicinski [this message]
2026-03-19 21:04   ` [PATCH net-next 0/9] pull request: ovpn 2026-03-17 Antonio Quartulli

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=20260319124432.2fda076a@kernel.org \
    --to=kuba@kernel.org \
    --cc=andrew+netdev@lunn.ch \
    --cc=antonio@openvpn.net \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=ralf@mandelbit.com \
    --cc=sd@queasysnail.net \
    /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