Netdev List
 help / color / mirror / Atom feed
From: Hyunwoo Kim <imv4bel@gmail.com>
To: Jakub Kicinski <kuba@kernel.org>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Kuniyuki Iwashima <kuniyu@google.com>,
	"David S . Miller" <davem@davemloft.net>,
	Eric Dumazet <edumazet@google.com>,
	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, stable@vger.kernel.org,
	imv4bel@gmail.com
Subject: Re: [PATCH v1 net-next 0/2] net: Disallow buggy TCP transitions and IPV6_ADDRFORM.
Date: Tue, 22 Sep 2026 09:42:28 +0900	[thread overview]
Message-ID: <arHO9Pk2DBzVOTLV@v4bel> (raw)
In-Reply-To: <20260921102310.49c9e008@kernel.org>

On Mon, Sep 21, 2026 at 10:23:10AM -0700, Jakub Kicinski wrote:
> On Sun, 20 Sep 2026 09:45:14 +0200 Greg Kroah-Hartman wrote:
> > On Sat, Sep 19, 2026 at 02:20:35PM -0700, Jakub Kicinski wrote:
> > > On Sat, 19 Sep 2026 07:35:05 +0900 Hyunwoo Kim wrote:  
> > > > What is the plan for stable backports here? Does the uapi change rule
> > > > this series out for stable?  
> > > 
> > > Not super well defined to be completely honest.
> > > My gut feeling is that we should wait for it to reach Linus, and ~rc3
> > > then pull it to LTS. Which would mean 2 months from now (mid Nov).  
> > 
> > Once it's in a released -rc, why not have it backported then?  Why wait?  :)
> 
> To be clear - it's in -next right now.
> 
> > > That said, I am personally pretty unbothered about local exploits.
> > > There's too many of them. And because of the serious exploits
> > > (remote, VM escape etc) I think people are not deploying stable
> > > much more rapidly and with less testing. I don't want to inject 
> > > a de-feature under such condition.
> > > 
> > > Adding Greg and stable in case they have a stronger stomach.  
> > 
> > I like to see the stable trees match Linus's whenever possible,
> > especially when we have known bugfixes.
> > 
> > > Also FWIW I believe that Eric D is AFK at the moment, and he's the only
> > > netdev maintainer subscribed to security@, AFAIU, so y'all may be aware
> > > of more things than I am...  
> > 
> > Not any more aware of anything other than the normal flood of crud...
> 
> Okay then, I think we should just wait for the merge window,
> and reevaluate if^w as new bugs show up.
> 
> Hyunwoo, if you have bugs in the queue that are solved in -next
> I'd hold off on sending the fixes unless they can be triggered
> remotely or from a VM.

OK, will do.


Best regards,
Hyunwoo Kim

      reply	other threads:[~2026-09-22  0:42 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
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 [this message]

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=arHO9Pk2DBzVOTLV@v4bel \
    --to=imv4bel@gmail.com \
    --cc=davem@davemloft.net \
    --cc=dsahern@kernel.org \
    --cc=edumazet@google.com \
    --cc=gregkh@linuxfoundation.org \
    --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=stable@vger.kernel.org \
    --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