Received-SPF: pass (google.com: domain of linux-kernel+bounces-84849-linux.lists.archive=gmail.com@vger.kernel.org designates 139.178.88.99 as permitted sender) client-ip=139.178.88.99;
Date: Wed, 28 Feb 2024 12:03:08 +0100
From: Petr =?UTF-8?B?VGVzYcWZw61r?= <petr@tesarici.cz>
To: "Linux regression tracking (Thorsten Leemhuis)"
 <regressions@leemhuis.info>
Cc: Linux regressions mailing list <regressions@lists.linux.dev>, Eric
 Dumazet <edumazet@google.com>, "David S. Miller" <davem@davemloft.net>,
 Paolo Abeni <pabeni@redhat.com>, Jakub Kicinski <kuba@kernel.org>, Jisheng
 Zhang <jszhang@kernel.org>, Alexandre Torgue
 <alexandre.torgue@foss.st.com>, Jose Abreu <joabreu@synopsys.com>, Maxime
 Coquelin <mcoquelin.stm32@gmail.com>, Chen-Yu Tsai <wens@csie.org>, Jernej
 Skrabec <jernej.skrabec@gmail.com>, Samuel Holland <samuel@sholland.org>,
 "open list:STMMAC ETHERNET DRIVER" <netdev@vger.kernel.org>, "moderated
 list:ARM/STM32 ARCHITECTURE" <linux-stm32@st-md-mailman.stormreply.com>,
 "moderated list:ARM/STM32 ARCHITECTURE"
 <linux-arm-kernel@lists.infradead.org>, open list
 <linux-kernel@vger.kernel.org>, "open list:ARM/Allwinner sunXi SoC support"
 <linux-sunxi@lists.linux.dev>, Marc Haber <mh+netdev@zugschlus.de>, Andrew
 Lunn <andrew@lunn.ch>, Florian Fainelli <f.fainelli@gmail.com>,
 stable@vger.kernel.org, alexis.lothore@bootlin.com, Guenter Roeck
 <linux@roeck-us.net>
Subject: Re: [PATCH net v3] net: stmmac: protect updates of 64-bit
 statistics counters
Message-ID: <20240228120308.48d6a9c2@meshulam.tesarici.cz>
In-Reply-To: <a3749d3f-ced1-4c48-adaf-348c8dee7610@leemhuis.info>
References: <20240203190927.19669-1-petr@tesarici.cz>
	<ea1567d9-ce66-45e6-8168-ac40a47d1821@roeck-us.net>
	<Zct5qJcZw0YKx54r@xhacker>
	<CANn89i+4tVWezqr=BYZ5AF=9EgV2EPqhdHun=u=ga32CEJ4BXQ@mail.gmail.com>
	<20d94512-c4f2-49f7-ac97-846dc24a6730@roeck-us.net>
	<CANn89iL1piwsbsBx4Z=kySUfmPa9LbZn-SNthgA+W6NEnojgSQ@mail.gmail.com>
	<a3749d3f-ced1-4c48-adaf-348c8dee7610@leemhuis.info>
Precedence: bulk
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

On Wed, 28 Feb 2024 07:19:56 +0100
"Linux regression tracking (Thorsten Leemhuis)" <regressions@leemhuis.info>=
 wrote:

> Net maintainers, chiming in here, as it seems handling this regression
> stalled.

Indeed, I was too busy with sandbox mode...

> On 13.02.24 16:52, Eric Dumazet wrote:
> > On Tue, Feb 13, 2024 at 4:26=E2=80=AFPM Guenter Roeck <linux@roeck-us.n=
et> wrote: =20
> >> On Tue, Feb 13, 2024 at 03:51:35PM +0100, Eric Dumazet wrote: =20
> >>> On Tue, Feb 13, 2024 at 3:29=E2=80=AFPM Jisheng Zhang <jszhang@kernel=
org> wrote: =20
> >>>> On Sun, Feb 11, 2024 at 08:30:21PM -0800, Guenter Roeck wrote: =20
> >>>>> On Sat, Feb 03, 2024 at 08:09:27PM +0100, Petr Tesarik wrote: =20
> >>>>>> As explained by a comment in <linux/u64_stats_sync.h>, write side =
of struct
> >>>>>> u64_stats_sync must ensure mutual exclusion, or one seqcount updat=
e could
> >>>>>> be lost on 32-bit platforms, thus blocking readers forever. Such l=
ockups
> >>>>>> have been observed in real world after stmmac_xmit() on one CPU ra=
ced with
> >>>>>> stmmac_napi_poll_tx() on another CPU.
> >>>>>>
> >>>>>> To fix the issue without introducing a new lock, split the statics=
 into
> >>>>>> three parts:
> >>>>>>
> >>>>>> 1. fields updated only under the tx queue lock,
> >>>>>> 2. fields updated only during NAPI poll,
> >>>>>> 3. fields updated only from interrupt context,
> >>>>>>
> >>>>>> Updates to fields in the first two groups are already serialized t=
hrough
> >>>>>> other locks. It is sufficient to split the existing struct u64_sta=
ts_sync
> >>>>>> so that each group has its own.
> >>>>>>
> >>>>>> Note that tx_set_ic_bit is updated from both contexts. Split this =
counter
> >>>>>> so that each context gets its own, and calculate their sum to get =
the total
> >>>>>> value in stmmac_get_ethtool_stats().
> >>>>>>
> >>>>>> For the third group, multiple interrupts may be processed by diffe=
rent CPUs
> >>>>>> at the same time, but interrupts on the same CPU will not nest. Mo=
ve fields
> >>>>>> from this group to a newly created per-cpu struct stmmac_pcpu_stat=
s.
> >>>>>>
> >>>>>> Fixes: 133466c3bbe1 ("net: stmmac: use per-queue 64 bit statistics=
 where necessary")
> >>>>>> Link: https://lore.kernel.org/netdev/Za173PhviYg-1qIn@torres.zugsc=
hlus.de/t/
> >>>>>> Cc: stable@vger.kernel.org
> >>>>>> Signed-off-by: Petr Tesarik <petr@tesarici.cz> =20
> >>>>>
> >>>>> This patch results in a lockdep splat. Backtrace and bisect results=
 attached.
> >>>>>
> >>>>> ---
> >>>>> [   33.736728] =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
> >>>>> [   33.736805] WARNING: inconsistent lock state
> >>>>> [   33.736953] 6.8.0-rc4 #1 Tainted: G                 N
> >>>>> [   33.737080] --------------------------------
> >>>>> [   33.737155] inconsistent {HARDIRQ-ON-W} -> {IN-HARDIRQ-W} usage.
> >>>>> [   33.737309] kworker/0:2/39 [HC1[1]:SC0[2]:HE0:SE0] takes:
> >>>>> [   33.737459] ef792074 (&syncp->seq#2){?...}-{0:0}, at: sun8i_dwma=
c_dma_interrupt+0x9c/0x28c
> >>>>> [   33.738206] {HARDIRQ-ON-W} state was registered at:
> >>>>> [   33.738318]   lock_acquire+0x11c/0x368
> >>>>> [   33.738431]   __u64_stats_update_begin+0x104/0x1ac
> >>>>> [   33.738525]   stmmac_xmit+0x4d0/0xc58 =20
> >>>>
> >>>> interesting lockdep splat...
> >>>> stmmac_xmit() operates on txq_stats->q_syncp, while the
> >>>> sun8i_dwmac_dma_interrupt() operates on pcpu's priv->xstats.pcpu_sta=
ts
> >>>> they are different syncp. so how does lockdep splat happen. =20
> >>>
> >>> Right, I do not see anything obvious yet. =20
> >>
> >> Wild guess: I think it maybe saying that due to
> >>
> >>         inconsistent {HARDIRQ-ON-W} -> {IN-HARDIRQ-W} usage.
> >>
> >> the critical code may somehow be interrupted and, while handling the
> >> interrupt, try to acquire the same lock again. =20
> >=20
> > This should not happen, the 'syncp' are different. They have different
> > lockdep classes.
> >=20
> > One is exclusively used from hard irq context.
> >=20
> > The second one only used from BH context. =20
>=20
> Alexis Lothor=C3=A9 hit this now as well, see yesterday report in this
> thread; apart from that nothing seem to have happened for two weeks now.
> The change recently made it to some stable/longterm kernels, too. Makes
> me wonder:
>=20
> What's the plan forward here? Is this considered to be a false positive?

Although my system has run stable for a couple of months, I am hesitant
to call it a false positive.

> Or a real problem?

That's what I think. But I would have to learn a lot about the network
stack to understand what exactly happens here.

It may go faster if somebody else on the Cc can give me a hint where to
start looking based on the lockdep warning.

Petr T