public inbox for netdev@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Jakub Kicinski <kuba@kernel.org>
Cc: Ilya Maximets <i.maximets@ovn.org>,
	Sasha Levin <sashal@kernel.org>,
	patches@lists.linux.dev, stable@vger.kernel.org,
	Eelco Chaudron <echaudro@redhat.com>,
	Simon Horman <horms@kernel.org>,
	aconole@redhat.com, netdev@vger.kernel.org, dev@openvswitch.org
Subject: Re: [PATCH AUTOSEL 6.15 044/118] openvswitch: Stricter validation for the userspace action
Date: Thu, 5 Jun 2025 16:45:39 +0200	[thread overview]
Message-ID: <2025060520-slacking-swimmer-1b31@gregkh> (raw)
In-Reply-To: <20250605072334.256dc524@kernel.org>

On Thu, Jun 05, 2025 at 07:23:34AM -0700, Jakub Kicinski wrote:
> On Wed, 4 Jun 2025 10:28:09 +0200 Greg KH wrote:
> > Nothing that ends up on Linus's tree should not be allowed also to be in
> > a stable kernel release as there is no difference in the "rule" that "we
> > will not break userspace".
> > 
> > So this isn't an issue here, if you need/want to make parsing more
> > strict, due to bugs or whatever, then great, let's make it more strict
> > as long as it doesn't break anyone's current system.  It doesn't matter
> > if this is in Linus's release or in a stable release, same rule holds
> > for both.
> 
> For sure, tho, I think the question is inverted here. We seem to be
> discussing arguments why something should not be backported, rather
> than arguments why something should be backported. You seem to be
> saying that the barrier of entry to stable is lower than what we'd
> normally send to Linus for an -rc, which perhaps makes sense in other
> parts of the kernel, but in networking that doesn't compute.
> 
> We go by simple logic of deciding if something is a fix. 
> This is not a fix. Neither is this:
> https://lore.kernel.org/all/20250604005049.4147522-54-sashal@kernel.org/

Ok, then that's a valid reason to drop it, that is not what I was
thinking was happening here at all, sorry.

greg k-h

  reply	other threads:[~2025-06-05 14:45 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20250604005049.4147522-1-sashal@kernel.org>
2025-06-04  0:48 ` [PATCH AUTOSEL 6.15 002/118] net: lan743x: Modify the EEPROM and OTP size for PCI1xxxx devices Sasha Levin
2025-06-04  0:48 ` [PATCH AUTOSEL 6.15 003/118] tipc: use kfree_sensitive() for aead cleanup Sasha Levin
2025-06-04  0:49 ` [PATCH AUTOSEL 6.15 009/118] emulex/benet: correct command version selection in be_cmd_get_stats() Sasha Levin
2025-06-04  0:49 ` [PATCH AUTOSEL 6.15 029/118] net: phy: mediatek: do not require syscon compatible for pio property Sasha Levin
2025-06-04  0:49 ` [PATCH AUTOSEL 6.15 035/118] tcp: always seek for minimal rtt in tcp_rcv_rtt_update() Sasha Levin
2025-06-04  0:49 ` [PATCH AUTOSEL 6.15 036/118] tcp: remove zero TCP TS samples for autotuning Sasha Levin
2025-06-04  0:49 ` [PATCH AUTOSEL 6.15 037/118] tcp: fix initial tp->rcvq_space.space value for passive TS enabled flows Sasha Levin
2025-06-04  0:49 ` [PATCH AUTOSEL 6.15 038/118] tcp: add receive queue awareness in tcp_rcv_space_adjust() Sasha Levin
2025-06-04  0:49 ` [PATCH AUTOSEL 6.15 040/118] ipv4/route: Use this_cpu_inc() for stats on PREEMPT_RT Sasha Levin
2025-06-04  0:49 ` [PATCH AUTOSEL 6.15 041/118] net: page_pool: Don't recycle into cache " Sasha Levin
2025-06-04  0:49 ` [PATCH AUTOSEL 6.15 042/118] xfrm: validate assignment of maximal possible SEQ number Sasha Levin
2025-06-04  0:49 ` [PATCH AUTOSEL 6.15 043/118] net: phy: marvell-88q2xxx: Enable temperature measurement in probe again Sasha Levin
2025-06-04  0:49 ` [PATCH AUTOSEL 6.15 044/118] openvswitch: Stricter validation for the userspace action Sasha Levin
2025-06-04  7:57   ` Ilya Maximets
2025-06-04  8:03     ` Greg KH
2025-06-04  8:19       ` Ilya Maximets
2025-06-04  8:28         ` Greg KH
2025-06-04  8:47           ` Ilya Maximets
2025-06-05 14:23           ` Jakub Kicinski
2025-06-05 14:45             ` Greg KH [this message]
2025-06-04  0:49 ` [PATCH AUTOSEL 6.15 045/118] net: atlantic: generate software timestamp just before the doorbell Sasha Levin
2025-06-04  0:49 ` [PATCH AUTOSEL 6.15 048/118] bpf: Pass the same orig_call value to trampoline functions Sasha Levin
2025-06-04  0:49 ` [PATCH AUTOSEL 6.15 049/118] net: stmmac: generate software timestamp just before the doorbell Sasha Levin
2025-06-04  0:49 ` [PATCH AUTOSEL 6.15 054/118] net: mlx4: add SOF_TIMESTAMPING_TX_SOFTWARE flag when getting ts info Sasha Levin
2025-06-04  0:50 ` [PATCH AUTOSEL 6.15 085/118] net: bridge: mcast: update multicast contex when vlan state is changed Sasha Levin
2025-06-04  0:50 ` [PATCH AUTOSEL 6.15 086/118] net: bridge: mcast: re-implement br_multicast_{enable, disable}_port functions Sasha Levin
2025-06-04  0:50 ` [PATCH AUTOSEL 6.15 088/118] bnxt_en: Remove unused field "ref_count" in struct bnxt_ulp Sasha Levin
2025-06-04  0:50 ` [PATCH AUTOSEL 6.15 105/118] usbnet: asix AX88772: leave the carrier control to phylink Sasha Levin
2025-06-04  0:50 ` [PATCH AUTOSEL 6.15 107/118] bpf, sockmap: Fix data lost during EAGAIN retries Sasha Levin
2025-06-04  0:50 ` [PATCH AUTOSEL 6.15 109/118] octeontx2-pf: Add error log forcn10k_map_unmap_rq_policer() Sasha Levin

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=2025060520-slacking-swimmer-1b31@gregkh \
    --to=greg@kroah.com \
    --cc=aconole@redhat.com \
    --cc=dev@openvswitch.org \
    --cc=echaudro@redhat.com \
    --cc=horms@kernel.org \
    --cc=i.maximets@ovn.org \
    --cc=kuba@kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=patches@lists.linux.dev \
    --cc=sashal@kernel.org \
    --cc=stable@vger.kernel.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