Linux kernel -stable discussions
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Pablo Neira Ayuso <pablo@netfilter.org>
Cc: netfilter-devel@vger.kernel.org, sashal@kernel.org,
	stable@vger.kernel.org
Subject: Re: [PATCH -stable,5.10.x 0/4] Netfilter fixes for -stable
Date: Tue, 13 Aug 2024 12:41:42 +0200	[thread overview]
Message-ID: <2024081333-factor-surprise-b366@gregkh> (raw)
In-Reply-To: <20240812102742.388214-1-pablo@netfilter.org>

On Mon, Aug 12, 2024 at 12:27:38PM +0200, Pablo Neira Ayuso wrote:
> Hi Greg, Sasha,
> 
> This batch contains a backport for recent fixes already upstream for 5.10.x.
> 
> The following list shows the backported patches, I am using original commit
> IDs for reference:
> 
> 1) b53c11664250 ("netfilter: nf_tables: set element extended ACK reporting support")
> 
>    This improves error reporting when adding more than one single element to set,
>    it is not specifically fixing up a crash.
> 
> 2) 7395dfacfff6 ("netfilter: nf_tables: use timestamp to check for set element timeout")
> 
> 3) fa23e0d4b756 ("netfilter: nf_tables: allow clone callbacks to sleep")
> 
> 4) cff3bd012a95 ("netfilter: nf_tables: prefer nft_chain_validate")
> 
> Please, apply,
> Thanks

Now queued up, thanks.

greg k-h

      parent reply	other threads:[~2024-08-13 10:41 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-12 10:27 [PATCH -stable,5.10.x 0/4] Netfilter fixes for -stable Pablo Neira Ayuso
2024-08-12 10:27 ` [PATCH -stable,5.10.x 1/4] netfilter: nf_tables: set element extended ACK reporting support Pablo Neira Ayuso
2024-08-12 10:27 ` [PATCH -stable,5.10.x 2/4] netfilter: nf_tables: use timestamp to check for set element timeout Pablo Neira Ayuso
2024-08-12 10:27 ` [PATCH -stable,5.10.x 3/4] netfilter: nf_tables: allow clone callbacks to sleep Pablo Neira Ayuso
2024-08-12 10:27 ` [PATCH -stable,5.10.x 4/4] netfilter: nf_tables: prefer nft_chain_validate Pablo Neira Ayuso
2024-08-13 10:41 ` Greg KH [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=2024081333-factor-surprise-b366@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=netfilter-devel@vger.kernel.org \
    --cc=pablo@netfilter.org \
    --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