From: Jakub Kicinski <kuba@kernel•org>
To: Fernando Fernandez Mancera <fmancera@suse•de>
Cc: netdev@vger•kernel.org, linux-kselftest@vger•kernel.org,
horms@kernel•org, pabeni@redhat•com, edumazet@google•com,
dsahern@kernel•org, davem@davemloft•net
Subject: Re: [PATCH 3/3 net-next v4] selftests: net: add test for IPv4 devconf netlink notifications
Date: Wed, 13 May 2026 19:35:44 -0700 [thread overview]
Message-ID: <20260513193544.47970cb8@kernel.org> (raw)
In-Reply-To: <20260510081528.5257-3-fmancera@suse.de>
On Sun, 10 May 2026 10:15:28 +0200 Fernando Fernandez Mancera wrote:
> Introduce a new test, `ipv4_devconf_notify`, to verify that the kernel
> sends the appropriate netlink notifications when IPv4 devconf parameters
> are modified.
>
> Since YNL currently has a bug where it declares an array of u32 values
> instead of the nested attributes expected by the kernel for devconf set
> operations, a temporary hack (`patched_add_attr`) is included to
> pack the netlink attributes correctly.
Right, YNL doesn't really support the level or weirdness that netconf
requires. Why use YNL? Can't we test this with iproute2?
nit: sashiko found a typo in "notificiation"
--
pw-bot: cr
next prev parent reply other threads:[~2026-05-14 2:35 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-10 8:15 [PATCH 1/3 net-next v4] ipv4: centralize devconf sysctl handling Fernando Fernandez Mancera
2026-05-10 8:15 ` [PATCH 2/3 net-next v4] ipv4: handle devconf post-set actions on netlink updates Fernando Fernandez Mancera
2026-05-14 2:30 ` Jakub Kicinski
2026-05-14 9:16 ` Fernando Fernandez Mancera
2026-05-10 8:15 ` [PATCH 3/3 net-next v4] selftests: net: add test for IPv4 devconf netlink notifications Fernando Fernandez Mancera
2026-05-14 2:35 ` Jakub Kicinski [this message]
2026-05-14 9:42 ` Fernando Fernandez Mancera
2026-05-14 23:24 ` Jakub Kicinski
2026-05-15 8:02 ` Fernando Fernandez Mancera
2026-05-16 1:16 ` Jakub Kicinski
2026-05-16 7:02 ` Fernando Fernandez Mancera
2026-05-18 21:23 ` Jakub Kicinski
2026-05-19 7:17 ` Paolo Abeni
2026-05-19 7:24 ` Fernando Fernandez Mancera
2026-05-25 15:53 ` Fernando Fernandez Mancera
2026-05-25 16:08 ` Jakub Kicinski
2026-05-25 17:12 ` Fernando Fernandez Mancera
2026-05-19 13:45 ` Nicolas Dichtel
2026-05-19 21:27 ` Fernando Fernandez Mancera
2026-05-20 7:22 ` Nicolas Dichtel
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=20260513193544.47970cb8@kernel.org \
--to=kuba@kernel$(echo .)org \
--cc=davem@davemloft$(echo .)net \
--cc=dsahern@kernel$(echo .)org \
--cc=edumazet@google$(echo .)com \
--cc=fmancera@suse$(echo .)de \
--cc=horms@kernel$(echo .)org \
--cc=linux-kselftest@vger$(echo .)kernel.org \
--cc=netdev@vger$(echo .)kernel.org \
--cc=pabeni@redhat$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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