public inbox for stable@vger.kernel.org
 help / color / mirror / Atom feed
From: Sasha Levin <sashal@kernel.org>
To: stable@vger.kernel.org
Cc: Pablo Neira Ayuso <pablo@netfilter.org>, Sasha Levin <sashal@kernel.org>
Subject: Re: [PATCH -stable,6.6 2/2] netfilter: nf_tables: use timestamp to check for set element timeout
Date: Wed, 19 Mar 2025 06:54:10 -0400	[thread overview]
Message-ID: <20250319065239-e7bcbc6a7aa34268@stable.kernel.org> (raw)
In-Reply-To: <20250318220305.224701-3-pablo@netfilter.org>

[ Sasha's backport helper bot ]

Hi,

✅ All tests passed successfully. No issues detected.
No action required from the submitter.

The upstream commit SHA1 provided is correct: 7395dfacfff65e9938ac0889dafa1ab01e987d15

Status in newer kernel trees:
6.13.y | Present (exact SHA1)
6.12.y | Present (exact SHA1)

Note: The patch differs from the upstream commit:
---
1:  7395dfacfff65 < -:  ------------- netfilter: nf_tables: use timestamp to check for set element timeout
-:  ------------- > 1:  594a1dd5138a6 Linux 6.6.83
---

Results of testing on various branches:

| Branch                    | Patch Apply | Build Test |
|---------------------------|-------------|------------|
| stable/linux-6.12.y       |  Success    |  Success   |

  reply	other threads:[~2025-03-19 10:54 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-18 22:03 [PATCH -stable,6.6 0/2] Netfilter fixes for -stable Pablo Neira Ayuso
2025-03-18 22:03 ` [PATCH -stable,6.6 1/2] netfilter: nf_tables: allow clone callbacks to sleep Pablo Neira Ayuso
2025-03-19 10:54   ` Sasha Levin
2025-03-18 22:03 ` [PATCH -stable,6.6 2/2] netfilter: nf_tables: use timestamp to check for set element timeout Pablo Neira Ayuso
2025-03-19 10:54   ` Sasha Levin [this message]
2025-03-18 22:08 ` [PATCH -stable,6.6 0/2] Netfilter fixes for -stable Pablo Neira Ayuso

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=20250319065239-e7bcbc6a7aa34268@stable.kernel.org \
    --to=sashal@kernel.org \
    --cc=pablo@netfilter.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