Linux kernel -stable discussions
 help / color / mirror / Atom feed
From: Christian Schmidbauer <opensource@grische.xyz>
To: stable@vger.kernel.org, Sasha Levin <sashal@kernel.org>
Cc: Christian Schmidbauer <opensource@grische.xyz>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Breno Leitao <leitao@debian.org>,
	Jeremy Kerr <jk@codeconstruct.com.au>,
	Guillaume Nault <gnault@redhat.com>,
	Eric Dumazet <edumazet@kernel.org>,
	Jakub Kicinski <kuba@kernel.org>
Subject: [PATCH 6.6.y 0/3] vxlan: fix stats reads after the dstats conversion
Date: Sun,  8 Nov 2026 17:19:34 +0100	[thread overview]
Message-ID: <cover.1794153876.git.opensource@grische.xyz> (raw)
In-Reply-To: <2026-09-26-daily-reply-0002-re-vxlan-dstats-6-6-reader-and-tx-side@kernel.org>

Hi Sasha,

This series backports the vxlan dstats reader side:

  3e2f544dd8a3 ("net: get stats64 if device if driver is configured")
  94b601bc4f85 ("net: core: Implement dstats-type stats collections")
  195f88c57737 ("vxlan: Remove generic .ndo_get_stats64")

3e2f544dd8a3 has no effect on 6.6 by itself, but is needed by
94b601bc4f85 to apply cleanly.

Tested on 6.6.161 with and without the series on two 32-bit boards, a
little-endian ARMv7 Aruba AP-325 and a big-endian PowerPC Enterasys
WS-AP3715i.

Both boards miss the vxlan drops without the series and count them with
it. On the AP-325 a stats read also hangs once rx_drops is odd, and the
series fixes that as well.

Breno Leitao (2):
  net: get stats64 if device if driver is configured
  vxlan: Remove generic .ndo_get_stats64

Jeremy Kerr (1):
  net: core: Implement dstats-type stats collections

 drivers/net/vxlan/vxlan_core.c |  2 --
 net/core/dev.c                 | 52 ++++++++++++++++++++++++++++++++++
 2 files changed, 52 insertions(+), 2 deletions(-)


base-commit: b5a1dc3ad4822c6edfb53429e9a3759c9b0ac2be
-- 
2.54.0


  reply	other threads:[~2026-11-08 16:19 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-05 11:35 FAILED: patch "[PATCH] vxlan: use pskb_network_may_pull() for transmit path header" failed to apply to 6.6-stable tree gregkh
2026-08-12  9:11 ` [PATCH 6.6.y 1/5] vxlan: Do not alloc tstats manually Sasha Levin
2026-08-12  9:11   ` [PATCH 6.6.y 2/5] net: core,vrf: Change pcpu_dstat fields to u64_stats_t Sasha Levin
2026-08-12  9:11   ` [PATCH 6.6.y 3/5] vrf: Make pcpu_dstats update functions available to other modules Sasha Levin
2026-08-12  9:11   ` [PATCH 6.6.y 4/5] vxlan: Handle stats using NETDEV_PCPU_STAT_DSTATS Sasha Levin
2026-09-25 18:08     ` Grische
2026-09-26 15:26       ` Sasha Levin
2026-11-08 16:19         ` Christian Schmidbauer [this message]
2026-11-08 16:19           ` [PATCH 6.6.y 1/3] net: get stats64 if device if driver is configured Christian Schmidbauer
2026-11-08 16:19           ` [PATCH 6.6.y 2/3] net: core: Implement dstats-type stats collections Christian Schmidbauer
2026-11-08 16:19           ` [PATCH 6.6.y 3/3] vxlan: Remove generic .ndo_get_stats64 Christian Schmidbauer
2026-08-12  9:11   ` [PATCH 6.6.y 5/5] vxlan: use pskb_network_may_pull() for transmit path header pulls 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=cover.1794153876.git.opensource@grische.xyz \
    --to=opensource@grische.xyz \
    --cc=edumazet@kernel.org \
    --cc=gnault@redhat.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=jk@codeconstruct.com.au \
    --cc=kuba@kernel.org \
    --cc=leitao@debian.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