From: Hyunwoo Kim <imv4bel@gmail.com>
To: Kuniyuki Iwashima <kuniyu@google.com>
Cc: "David S . Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Neal Cardwell <ncardwell@google.com>,
Willem de Bruijn <willemb@google.com>,
David Ahern <dsahern@kernel.org>,
Ido Schimmel <idosch@nvidia.com>, Simon Horman <horms@kernel.org>,
Kuniyuki Iwashima <kuni1840@gmail.com>,
netdev@vger.kernel.org, imv4bel@gmail.com
Subject: Re: [PATCH v1 net-next 0/2] net: Disallow buggy TCP transitions and IPV6_ADDRFORM.
Date: Sat, 19 Sep 2026 07:35:05 +0900 [thread overview]
Message-ID: <aq28mdNpi3ssjgXz@v4bel> (raw)
In-Reply-To: <20260904033543.2635540-1-kuniyu@google.com>
On Fri, Sep 04, 2026 at 03:35:27AM +0000, Kuniyuki Iwashima wrote:
> The following operations have recently received a lot of AI-driven
> bug reports:
>
> * listen() + shutdown() + connect()
> * connect() + connect(AF_UNSPEC) + listen()
>
> * setsockopt(IPV6_ADDRFORM)
>
> They are not worth fixing by churning the fast path, so this series
> disallows the transitions and removes IPV6_ADDRFORM.
>
> https://lore.kernel.org/netdev/CANn89i+px52TtJy3S9=uHxGj3s-WueguRo1Z_4FxO=02KLmwmQ@mail.gmail.com/
> https://lore.kernel.org/netdev/5832ba17-c096-4f07-aa73-2e2bb6f79856@redhat.com/
>
> I did not add Fixes tags, but if we want to backport, the tag
> would be:
>
> Fixes: 1da177e4c3f4 ("Linux-2.6.12-rc2")
Hi netdev maintainers,
What is the plan for stable backports here? Does the uapi change rule
this series out for stable?
>
>
> Kuniyuki Iwashima (2):
> tcp: Do not allow buggy transitions between ehash and lhash2.
> ipv6: Remove IPV6_ADDRFORM.
>
> include/linux/net.h | 2 +-
> include/net/inet_connection_sock.h | 1 +
> net/core/sock.c | 4 +-
> net/ipv4/af_inet.c | 3 --
> net/ipv4/inet_connection_sock.c | 1 +
> net/ipv4/inet_hashtables.c | 11 ++++
> net/ipv6/af_inet6.c | 4 --
> net/ipv6/ipv6_sockglue.c | 87 ------------------------------
> 8 files changed, 15 insertions(+), 98 deletions(-)
>
> --
> 2.55.0.1003.g10538fe699-goog
>
Best regards,
Hyunwoo Kim
next prev parent reply other threads:[~2026-09-18 22:35 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-04 3:35 [PATCH v1 net-next 0/2] net: Disallow buggy TCP transitions and IPV6_ADDRFORM Kuniyuki Iwashima
2026-09-04 3:35 ` [PATCH v1 net-next 1/2] tcp: Do not allow buggy transitions between ehash and lhash2 Kuniyuki Iwashima
2026-09-04 11:32 ` Jakub Sitnicki
2026-09-07 4:19 ` netdev-bot+sashiko
2026-09-17 12:49 ` Daniel Zahka
2026-09-17 18:36 ` Kuniyuki Iwashima
2026-09-04 3:35 ` [PATCH v1 net-next 2/2] ipv6: Remove IPV6_ADDRFORM Kuniyuki Iwashima
2026-09-04 9:10 ` Paolo Abeni
2026-09-07 4:19 ` netdev-bot+sashiko
2026-09-08 9:21 ` David Laight
2026-09-08 1:00 ` [PATCH v1 net-next 0/2] net: Disallow buggy TCP transitions and IPV6_ADDRFORM patchwork-bot+netdevbpf
2026-09-18 22:35 ` Hyunwoo Kim [this message]
2026-09-19 21:20 ` Jakub Kicinski
2026-09-20 7:45 ` Greg Kroah-Hartman
2026-09-21 17:23 ` Jakub Kicinski
2026-09-22 0:42 ` Hyunwoo Kim
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=aq28mdNpi3ssjgXz@v4bel \
--to=imv4bel@gmail.com \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=idosch@nvidia.com \
--cc=kuba@kernel.org \
--cc=kuni1840@gmail.com \
--cc=kuniyu@google.com \
--cc=ncardwell@google.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=willemb@google.com \
/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