public inbox for stable@vger.kernel.org
 help / color / mirror / Atom feed
From: Florian Westphal <fw@strlen.de>
To: Gianluca Anzolin <gianluca@sottospazio.it>
Cc: netfilter-devel@vger.kernel.org, stable@vger.kernel.org
Subject: Re: Request for a backport to Linux v5.4
Date: Tue, 24 Aug 2021 17:46:29 +0200	[thread overview]
Message-ID: <20210824154629.GA6610@breakpoint.cc> (raw)
In-Reply-To: <c1088b68-1804-d009-9627-d649162cdfff@sottospazio.it>

Gianluca Anzolin <gianluca@sottospazio.it> wrote:

[ CC stable ]

> I'm writing to request a backport of the following commit:
> 
>    2e34328b396a netfilter: nft_exthdr: fix endianness of tcp option cast
> to the stable version of Linux v5.4.

Hello stable maintainers, can you please pick this change
for 5.4, 4.19 and 4.14?

It applies cleanly to all of those branches.
I'll leave rest as full-quote for context.

> This bugfix never landed to Linux v5.4: a later similar endianness bugfix
> (b428336676db) instead did (see commit 666d1d1a0584).
> 
> The aforementioned commit fixes an endianness bug in the mangling of the MSS
> tcp option for nftables.
> 
> This bug bites hard big-endian routers (MIPS for example) running the PPPoE
> stack and nftables.
> 
> The following rule:
> 
>     nft add rule ip filter forward tcp flags syn tcp option maxseg size set
> rt mtu
> 
> instead of changing the MSS value the one in the routing cache, ZEROES it,
> disrupting the tcp connections.
> 
> A backport would be nice because Linux v5.4 is the release used in the
> upcoming stable release of OpenWRT (21.02).
> 
> I already submitted a bug-report to OpenWRT a few weeks ago but I've got no
> answer yet maybe because they still use iptables as the default netfilter
> tool, even if they offer nftables as an alternative.
> 
> Still I think this bug should be fixed in the stable versions of the kernel.
> 
> This way it will also come to OpenWRT when they update the kernel to the
> latest minor version, even if the maintainers don't see the my bug report is
> ignored.
> 
> I'd like to thank you for the attention you paid to this message even if I
> probably didn't follow the right process for reporting the problem.
> 
> Regards,
> 
> Gianluca Anzolin

       reply	other threads:[~2021-08-24 15:46 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <c1088b68-1804-d009-9627-d649162cdfff@sottospazio.it>
2021-08-24 15:46 ` Florian Westphal [this message]
2021-08-24 16:30   ` Request for a backport to Linux v5.4 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=20210824154629.GA6610@breakpoint.cc \
    --to=fw@strlen.de \
    --cc=gianluca@sottospazio.it \
    --cc=netfilter-devel@vger.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