All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Petr Tesarik <petr@tesarici.cz>
Cc: alexandre.torgue@foss.st.com, joabreu@synopsys.com,
	davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
	pabeni@redhat.com, mcoquelin.stm32@gmail.com, wens@csie.org,
	jernej.skrabec@gmail.com, samuel@sholland.org,
	jszhang@kernel.org, netdev@vger.kernel.org,
	linux-stm32@st-md-mailman.stormreply.com,
	linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org, linux-sunxi@lists.linux.dev,
	mh+netdev@zugschlus.de, andrew@lunn.ch, f.fainelli@gmail.com,
	stable@vger.kernel.org
Subject: Re: [PATCH net v3] net: stmmac: protect updates of 64-bit statistics counters
Date: Wed, 07 Feb 2024 09:10:25 +0000	[thread overview]
Message-ID: <170729702541.31522.8754905006786635767.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240203190927.19669-1-petr@tesarici.cz>

Hello:

This patch was applied to netdev/net.git (main)
by David S. Miller <davem@davemloft.net>:

On Sat,  3 Feb 2024 20:09:27 +0100 you wrote:
> 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 update could
> be lost on 32-bit platforms, thus blocking readers forever. Such lockups
> have been observed in real world after stmmac_xmit() on one CPU raced with
> stmmac_napi_poll_tx() on another CPU.
> 
> To fix the issue without introducing a new lock, split the statics into
> three parts:
> 
> [...]

Here is the summary with links:
  - [net,v3] net: stmmac: protect updates of 64-bit statistics counters
    https://git.kernel.org/netdev/net/c/38cc3c6dcc09

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



WARNING: multiple messages have this Message-ID (diff)
From: patchwork-bot+netdevbpf@kernel.org
To: Petr Tesarik <petr@tesarici.cz>
Cc: alexandre.torgue@foss.st.com, joabreu@synopsys.com,
	davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
	pabeni@redhat.com, mcoquelin.stm32@gmail.com, wens@csie.org,
	jernej.skrabec@gmail.com, samuel@sholland.org,
	jszhang@kernel.org, netdev@vger.kernel.org,
	linux-stm32@st-md-mailman.stormreply.com,
	linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org, linux-sunxi@lists.linux.dev,
	mh+netdev@zugschlus.de, andrew@lunn.ch, f.fainelli@gmail.com,
	stable@vger.kernel.org
Subject: Re: [PATCH net v3] net: stmmac: protect updates of 64-bit statistics counters
Date: Wed, 07 Feb 2024 09:10:25 +0000	[thread overview]
Message-ID: <170729702541.31522.8754905006786635767.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240203190927.19669-1-petr@tesarici.cz>

Hello:

This patch was applied to netdev/net.git (main)
by David S. Miller <davem@davemloft.net>:

On Sat,  3 Feb 2024 20:09:27 +0100 you wrote:
> 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 update could
> be lost on 32-bit platforms, thus blocking readers forever. Such lockups
> have been observed in real world after stmmac_xmit() on one CPU raced with
> stmmac_napi_poll_tx() on another CPU.
> 
> To fix the issue without introducing a new lock, split the statics into
> three parts:
> 
> [...]

Here is the summary with links:
  - [net,v3] net: stmmac: protect updates of 64-bit statistics counters
    https://git.kernel.org/netdev/net/c/38cc3c6dcc09

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  parent reply	other threads:[~2024-02-07  9:10 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-03 19:09 [PATCH net v3] net: stmmac: protect updates of 64-bit statistics counters Petr Tesarik
2024-02-03 19:09 ` Petr Tesarik
2024-02-04  4:21 ` Jisheng Zhang
2024-02-04  4:21   ` Jisheng Zhang
2024-02-07  9:10 ` patchwork-bot+netdevbpf [this message]
2024-02-07  9:10   ` patchwork-bot+netdevbpf
2024-02-12  4:30 ` Guenter Roeck
2024-02-12  4:30   ` Guenter Roeck
2024-02-13 14:16   ` Jisheng Zhang
2024-02-13 14:16     ` Jisheng Zhang
2024-02-13 14:51     ` Eric Dumazet
2024-02-13 14:51       ` Eric Dumazet
2024-02-13 15:26       ` Guenter Roeck
2024-02-13 15:26         ` Guenter Roeck
2024-02-13 15:52         ` Eric Dumazet
2024-02-13 15:52           ` Eric Dumazet
2024-02-27  9:40           ` Alexis Lothoré
2024-02-27  9:40             ` Alexis Lothoré
2024-02-28  6:19           ` Linux regression tracking (Thorsten Leemhuis)
2024-02-28  6:19             ` Linux regression tracking (Thorsten Leemhuis)
2024-02-28 11:03             ` Petr Tesařík
2024-02-28 11:03               ` Petr Tesařík
2024-03-06  8:23               ` Linux regression tracking (Thorsten Leemhuis)
2024-03-06  8:23                 ` Linux regression tracking (Thorsten Leemhuis)
2024-03-06  9:01                 ` Petr Tesařík
2024-03-06  9:01                   ` Petr Tesařík
2024-03-06 10:03                   ` Petr Tesařík
2024-03-06 10:03                     ` Petr Tesařík
2024-03-06 10:17                     ` Eric Dumazet
2024-03-06 10:17                       ` Eric Dumazet
2024-02-26 17:41   ` Guenter Roeck
2024-02-26 17:41     ` Guenter Roeck

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=170729702541.31522.8754905006786635767.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=alexandre.torgue@foss.st.com \
    --cc=andrew@lunn.ch \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=f.fainelli@gmail.com \
    --cc=jernej.skrabec@gmail.com \
    --cc=joabreu@synopsys.com \
    --cc=jszhang@kernel.org \
    --cc=kuba@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-stm32@st-md-mailman.stormreply.com \
    --cc=linux-sunxi@lists.linux.dev \
    --cc=mcoquelin.stm32@gmail.com \
    --cc=mh+netdev@zugschlus.de \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=petr@tesarici.cz \
    --cc=samuel@sholland.org \
    --cc=stable@vger.kernel.org \
    --cc=wens@csie.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.