From: Simon Horman <horms@kernel.org>
To: Antonio Quartulli <antonio@openvpn.net>
Cc: netdev@vger.kernel.org, Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Donald Hunter <donald.hunter@gmail.com>,
Shuah Khan <shuah@kernel.org>,
sd@queasysnail.net, ryazanov.s.a@gmail.com,
Andrew Lunn <andrew+netdev@lunn.ch>,
linux-kernel@vger.kernel.org, linux-kselftest@vger.kernel.org,
Shuah Khan <skhan@linuxfoundation.org>
Subject: Re: [PATCH net-next v14 22/22] testing/selftests: add test tool and scripts for ovpn module
Date: Tue, 10 Dec 2024 16:47:15 +0000 [thread overview]
Message-ID: <20241210164715.GB6554@kernel.org> (raw)
In-Reply-To: <20241209-b4-ovpn-v14-22-ea243cf16417@openvpn.net>
On Mon, Dec 09, 2024 at 09:53:31AM +0100, Antonio Quartulli wrote:
> The ovpn-cli tool can be compiled and used as selftest for the ovpn
> kernel module.
>
> [NOTE: it depends on libmedtls for decoding base64-encoded keys]
>
> ovpn-cli implements the netlink and RTNL APIs and can thus be integrated
> in any script for more automated testing.
>
> Along with the tool, 4 scripts are provided that perform basic
> functionality tests by means of network namespaces.
> These scripts take part to the kselftest automation.
>
> The output of the scripts, which will appear in the kselftest
> reports, is a list of steps performed by the scripts plus some
> output coming from the execution of `ping`, `iperf` and `ovpn-cli`
> itself.
> In general it is useful only in case of failure, in order to
> understand which step has failed and why.
>
> Cc: linux-kselftest@vger.kernel.org
> Signed-off-by: Antonio Quartulli <antonio@openvpn.net>
> Reviewed-by: Shuah Khan <skhan@linuxfoundation.org>
...
> +/**
> + * Helper function used to easily add attributes to a rtnl message
> + */
Hi Antonio,
This comment starts with a '/**' but is otherwise not formatted as
a Kernel doc. Probably it is best to simply start the comment with '/*'.
Likewise elsewhere in this patch.
Flagged by ./scripts/kernel-doc -none
> +static int ovpn_addattr(struct nlmsghdr *n, int maxlen, int type,
> + const void *data, int alen)
...
next prev parent reply other threads:[~2024-12-10 16:47 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-09 8:53 [PATCH net-next v14 00/22] Introducing OpenVPN Data Channel Offload Antonio Quartulli
2024-12-09 8:53 ` [PATCH net-next v14 01/22] net: introduce OpenVPN Data Channel Offload (ovpn) Antonio Quartulli
2024-12-09 8:53 ` [PATCH net-next v14 02/22] ovpn: add basic netlink support Antonio Quartulli
2024-12-09 8:53 ` [PATCH net-next v14 03/22] ovpn: add basic interface creation/destruction/management routines Antonio Quartulli
2024-12-09 8:53 ` [PATCH net-next v14 04/22] ovpn: keep carrier always on for MP interfaces Antonio Quartulli
2024-12-09 8:53 ` [PATCH net-next v14 05/22] ovpn: introduce the ovpn_peer object Antonio Quartulli
2024-12-09 8:53 ` [PATCH net-next v14 06/22] ovpn: introduce the ovpn_socket object Antonio Quartulli
2024-12-09 8:53 ` [PATCH net-next v14 07/22] ovpn: implement basic TX path (UDP) Antonio Quartulli
2024-12-09 8:53 ` [PATCH net-next v14 08/22] ovpn: implement basic RX " Antonio Quartulli
2024-12-10 16:44 ` Simon Horman
2024-12-11 10:00 ` Antonio Quartulli
2024-12-09 8:53 ` [PATCH net-next v14 09/22] ovpn: implement packet processing Antonio Quartulli
2024-12-09 8:53 ` [PATCH net-next v14 10/22] ovpn: store tunnel and transport statistics Antonio Quartulli
2024-12-09 8:53 ` [PATCH net-next v14 11/22] ovpn: implement TCP transport Antonio Quartulli
2024-12-09 8:53 ` [PATCH net-next v14 12/22] ovpn: implement multi-peer support Antonio Quartulli
2024-12-09 8:53 ` [PATCH net-next v14 13/22] ovpn: implement peer lookup logic Antonio Quartulli
2024-12-09 8:53 ` [PATCH net-next v14 14/22] ovpn: implement keepalive mechanism Antonio Quartulli
2024-12-09 8:53 ` [PATCH net-next v14 15/22] ovpn: add support for updating local UDP endpoint Antonio Quartulli
2024-12-09 8:53 ` [PATCH net-next v14 16/22] ovpn: add support for peer floating Antonio Quartulli
2024-12-09 8:53 ` [PATCH net-next v14 17/22] ovpn: implement peer add/get/dump/delete via netlink Antonio Quartulli
2024-12-11 3:08 ` Xiao Liang
2024-12-11 11:31 ` Antonio Quartulli
2024-12-11 12:35 ` Xiao Liang
2024-12-11 12:52 ` Antonio Quartulli
2024-12-11 13:53 ` Xiao Liang
2024-12-11 14:07 ` Antonio Quartulli
2024-12-11 14:37 ` Xiao Liang
2024-12-09 8:53 ` [PATCH net-next v14 18/22] ovpn: implement key add/get/del/swap " Antonio Quartulli
2024-12-09 8:53 ` [PATCH net-next v14 19/22] ovpn: kill key and notify userspace in case of IV exhaustion Antonio Quartulli
2024-12-09 8:53 ` [PATCH net-next v14 20/22] ovpn: notify userspace when a peer is deleted Antonio Quartulli
2024-12-09 8:53 ` [PATCH net-next v14 21/22] ovpn: add basic ethtool support Antonio Quartulli
2024-12-09 8:53 ` [PATCH net-next v14 22/22] testing/selftests: add test tool and scripts for ovpn module Antonio Quartulli
2024-12-10 16:47 ` Simon Horman [this message]
2024-12-11 10:01 ` 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=20241210164715.GB6554@kernel.org \
--to=horms@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=antonio@openvpn.net \
--cc=donald.hunter@gmail.com \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=ryazanov.s.a@gmail.com \
--cc=sd@queasysnail.net \
--cc=shuah@kernel.org \
--cc=skhan@linuxfoundation.org \
/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;
as well as URLs for NNTP newsgroup(s).