From: Jakub Kicinski <kuba@kernel.org>
To: Ido Schimmel <idosch@nvidia.com>
Cc: Quentin Armitage <quentin@armitage.org.uk>,
David Ahern <dsahern@kernel.org>,
netdev@vger.kernel.org
Subject: Re: net: parsing IFLA_INET_CONF broken since 7.1 if NLA_F_NESTED not set
Date: Mon, 14 Sep 2026 10:51:24 -0700 [thread overview]
Message-ID: <20260914105124.4a3abc1e@kernel.org> (raw)
In-Reply-To: <20260914174307.GA450786@shredder>
On Mon, 14 Sep 2026 20:43:07 +0300 Ido Schimmel wrote:
> > Please explain how you discovered the problem.
> > Is there some open source or closed source SW you're aware of which
> > breaks?
>
> FWIW, I sent a patch to keepalived in the past and I remember Quentin
> from there. It seems to be affected:
Ah, thanks! I was (of course) worried it's an AI report :S
next prev parent reply other threads:[~2026-09-14 17:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-14 14:21 net: parsing IFLA_INET_CONF broken since 7.1 if NLA_F_NESTED not set Quentin Armitage
2026-09-14 15:27 ` Ido Schimmel
2026-09-14 15:42 ` Ido Schimmel
2026-09-14 17:21 ` Jakub Kicinski
2026-09-14 17:43 ` Ido Schimmel
2026-09-14 17:51 ` Jakub Kicinski [this message]
2026-09-14 17:52 ` Quentin Armitage
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=20260914105124.4a3abc1e@kernel.org \
--to=kuba@kernel.org \
--cc=dsahern@kernel.org \
--cc=idosch@nvidia.com \
--cc=netdev@vger.kernel.org \
--cc=quentin@armitage.org.uk \
/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