public inbox for stable@vger.kernel.org
 help / color / mirror / Atom feed
From: Sasha Levin <sashal@kernel.org>
To: stable@vger.kernel.org
Cc: Felix Moessbauer <felix.moessbauer@siemens.com>,
	Sasha Levin <sashal@kernel.org>
Subject: Re: [PATCH 6.1.y 6.6.y 1/1] netfilter: nft_counter: Use u64_stats_t for statistic.
Date: Thu, 20 Mar 2025 12:03:46 -0400	[thread overview]
Message-ID: <20250320115029-c17a5a20b63e96df@stable.kernel.org> (raw)
In-Reply-To: <20250320124108.338412-1-felix.moessbauer@siemens.com>

[ 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: 4a1d3acd6ea86075e77fcc1188c3fc372833ba73

WARNING: Author mismatch between patch and upstream commit:
Backport author: Felix Moessbauer<felix.moessbauer@siemens.com>
Commit author: Sebastian Andrzej Siewior<bigeasy@linutronix.de>

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

Note: The patch differs from the upstream commit:
---
1:  4a1d3acd6ea86 ! 1:  348975e270b55 netfilter: nft_counter: Use u64_stats_t for statistic.
    @@ Metadata
      ## Commit message ##
         netfilter: nft_counter: Use u64_stats_t for statistic.
     
    +    commit 4a1d3acd6ea86075e77fcc1188c3fc372833ba73 upstream.
    +
         The nft_counter uses two s64 counters for statistics. Those two are
         protected by a seqcount to ensure that the 64bit variable is always
         properly seen during updates even on 32bit architectures where the store
    @@ Commit message
         Cc: Eric Dumazet <edumazet@google.com>
         Signed-off-by: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
         Signed-off-by: Pablo Neira Ayuso <pablo@netfilter.org>
    +    Signed-off-by: Felix Moessbauer <felix.moessbauer@siemens.com>
     
      ## net/netfilter/nft_counter.c ##
     @@
---

Results of testing on various branches:

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

      reply	other threads:[~2025-03-20 16:03 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-20 12:41 [PATCH 6.1.y 6.6.y 1/1] netfilter: nft_counter: Use u64_stats_t for statistic Felix Moessbauer
2025-03-20 16:03 ` Sasha Levin [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=20250320115029-c17a5a20b63e96df@stable.kernel.org \
    --to=sashal@kernel.org \
    --cc=felix.moessbauer@siemens.com \
    --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