All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Thorsten Leemhuis <regressions@leemhuis.info>
Cc: Jindrich Makovicka <makovick@gmail.com>,
	Genes Lists <lists@sapience.com>,
	Greg KH <gregkh@linuxfoundation.org>,
	linux-kernel@vger.kernel.org, coreteam@netfilter.org,
	netfilter-devel@vger.kernel.org, stable@vger.kernel.org,
	regressions@lists.linux.dev,
	"Kris Karas (Bug Reporting)" <bugs-a21@moonlit-rail.com>
Subject: Re: [REGRESSION] 6.19.4 stable netfilter / nftables [resolved]
Date: Wed, 4 Mar 2026 12:09:44 +0100	[thread overview]
Message-ID: <aagS-IUhQwz6m3MF@chamomile> (raw)
In-Reply-To: <75a4115f-e7f3-4316-b046-525fcd87cdef@leemhuis.info>

On Wed, Mar 04, 2026 at 06:50:32AM +0100, Thorsten Leemhuis wrote:
> On 3/3/26 23:03, Pablo Neira Ayuso wrote:
>  
> > A new userspace release with this fix is required.
> 
> But a new user space should never be required for a new kernel. Find a
> few quotes from Linus on this below. And I noticed other people ran
> into this, too, so it's not a corner case:
> https://lore.kernel.org/all/aaeIDJigEVkDfrRg@chamomile/
> 
> So should this be reverted everywhere where this was applied? Or is
> there some way to do what the commit wanted to do without breaking
> userspace?

Thanks for explaining.

I kindly requested to revert in -stable:

  netfilter: nft_set_rbtree: validate open interval overlap

which amplifies the userspace bug.

      reply	other threads:[~2026-03-04 11:09 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-27  3:46 [REGRESSION] 6.19.4 stable netfilter / nftables Genes Lists
2026-02-27  8:00 ` Thorsten Leemhuis
2026-02-27  8:13   ` Florian Westphal
2026-02-27 18:58     ` [REGRESSION] 6.19.4 stable netfilter / nftables -> resolved Genes Lists
2026-02-27 12:23   ` [REGRESSION] 6.19.4 stable netfilter / nftables Genes Lists
2026-02-27 13:12     ` [REGRESSION] 6.19.4 stable netfilter / nftables [resolved] Genes Lists
2026-02-27 13:17       ` Greg KH
2026-02-27 13:39         ` Genes Lists
2026-03-03  7:00           ` Jindrich Makovicka
2026-03-03  7:31             ` Thorsten Leemhuis
2026-03-03 17:32               ` Jindrich Makovicka
2026-03-03 18:44                 ` Florian Westphal
2026-03-03 22:03             ` Pablo Neira Ayuso
2026-03-04  5:50               ` Thorsten Leemhuis
2026-03-04 11:09                 ` Pablo Neira Ayuso [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=aagS-IUhQwz6m3MF@chamomile \
    --to=pablo@netfilter.org \
    --cc=bugs-a21@moonlit-rail.com \
    --cc=coreteam@netfilter.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lists@sapience.com \
    --cc=makovick@gmail.com \
    --cc=netfilter-devel@vger.kernel.org \
    --cc=regressions@leemhuis.info \
    --cc=regressions@lists.linux.dev \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.