From: Simon Horman <simon.horman@corigine.com>
To: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
Cc: netdev@vger.kernel.org, Jakub Kicinski <kuba@kernel.org>,
"David S. Miller" <davem@davemloft.net>,
Thomas Gleixner <tglx@linutronix.de>,
Peter Zijlstra <peterz@infradead.org>,
Catherine Sullivan <csully@google.com>,
David Awogbemila <awogbemila@google.com>,
Dimitris Michailidis <dmichail@fungible.com>,
Eric Dumazet <edumazet@google.com>,
Hans Ulli Kroll <ulli.kroll@googlemail.com>,
Jeroen de Borst <jeroendb@google.com>,
Johannes Berg <johannes@sipsolutions.net>,
Linus Walleij <linus.walleij@linaro.org>,
Paolo Abeni <pabeni@redhat.com>,
linux-arm-kernel@lists.infradead.org,
linux-wireless@vger.kernel.org, oss-drivers@corigine.com,
stable@vger.kernel.org
Subject: Re: [PATCH net 2/2] net: Use u64_stats_fetch_begin_irq() for stats fetch.
Date: Mon, 29 Aug 2022 11:55:26 +0200 [thread overview]
Message-ID: <YwyNDi3p72DBvZ/3@corigine.com> (raw)
In-Reply-To: <20220825113645.212996-3-bigeasy@linutronix.de>
On Thu, Aug 25, 2022 at 01:36:45PM +0200, Sebastian Andrzej Siewior wrote:
> On 32bit-UP u64_stats_fetch_begin() disables only preemption. If the
> reader is in preemptible context and the writer side
> (u64_stats_update_begin*()) runs in an interrupt context (IRQ or
> softirq) then the writer can update the stats during the read operation.
> This update remains undetected.
>
> Use u64_stats_fetch_begin_irq() to ensure the stats fetch on 32bit-UP
> are not interrupted by a writer. 32bit-SMP remains unaffected by this
> change.
Thanks,
for the NFP driver portion:
Reviewed-by: Simon Horman <simon.horman@corigine.com>
prev parent reply other threads:[~2022-08-29 9:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20220825113645.212996-1-bigeasy@linutronix.de>
2022-08-25 11:36 ` [PATCH net 2/2] net: Use u64_stats_fetch_begin_irq() for stats fetch Sebastian Andrzej Siewior
2022-08-29 9:55 ` Simon Horman [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=YwyNDi3p72DBvZ/3@corigine.com \
--to=simon.horman@corigine.com \
--cc=awogbemila@google.com \
--cc=bigeasy@linutronix.de \
--cc=csully@google.com \
--cc=davem@davemloft.net \
--cc=dmichail@fungible.com \
--cc=edumazet@google.com \
--cc=jeroendb@google.com \
--cc=johannes@sipsolutions.net \
--cc=kuba@kernel.org \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-wireless@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=oss-drivers@corigine.com \
--cc=pabeni@redhat.com \
--cc=peterz@infradead.org \
--cc=stable@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=ulli.kroll@googlemail.com \
/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