Linux kernel -stable discussions
 help / color / mirror / Atom feed
From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Abdifatah Suruur <suruurism@gmail.com>
Cc: stable@vger.kernel.org, Florian Westphal <fw@strlen.de>,
	Greg KH <gregkh@linuxfoundation.org>,
	Sasha Levin <sashal@kernel.org>
Subject: Re: [PATCH 6.18.y 1/2] Revert "netfilter: nft_byteorder: remove multi-register support"
Date: Mon, 9 Nov 2026 13:25:59 +0100	[thread overview]
Message-ID: <avG71wG3PHvRQT0B@chamomile> (raw)
In-Reply-To: <179422702651.5131.4174988605567778384@gmail.com>

On Mon, Nov 09, 2026 at 03:23:46PM +0300, Abdifatah Suruur wrote:
> This reverts commit dc29c0478b8564feb9371e715b5a0016eb8903fd.
> 
> The upstream change removes multi-register byteorder support and is
> tagged stable+noautosel because nftables versions before 1.1.0 can
> generate length/size combinations that the removal rejects.  Backporting
> it to stable can make existing rulesets fail to load.

Same thing here, if this can break stuff, this cannot be taken as is.

  reply	other threads:[~2026-11-09 12:26 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-09 12:23 [PATCH 6.18.y 0/2] nft_byteorder: fix the uninitialised-stack read without removing multi-register support Abdifatah Suruur
2026-11-09 12:23 ` [PATCH 6.18.y 1/2] Revert "netfilter: nft_byteorder: remove multi-register support" Abdifatah Suruur
2026-11-09 12:25   ` Pablo Neira Ayuso [this message]
2026-11-09 12:35     ` Pablo Neira Ayuso
2026-11-09 13:18       ` Abdifatah Suruur
2026-11-09 12:23 ` [PATCH 6.18.y 2/2] netfilter: nft_byteorder: initialise the marked destination span Abdifatah Suruur

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=avG71wG3PHvRQT0B@chamomile \
    --to=pablo@netfilter.org \
    --cc=fw@strlen.de \
    --cc=gregkh@linuxfoundation.org \
    --cc=sashal@kernel.org \
    --cc=stable@vger.kernel.org \
    --cc=suruurism@gmail.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