From: Greg KH <gregkh@linuxfoundation.org>
To: Doug Berger <opendmb@gmail.com>
Cc: stable@vger.kernel.org, Florian Fainelli <f.fainelli@gmail.com>,
"David S. Miller" <davem@davemloft.net>,
bcm-kernel-feedback-list@broadcom.com, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH stable 5.4 0/3] net: bcmgenet: protect contended accesses
Date: Thu, 23 May 2024 13:31:32 +0200 [thread overview]
Message-ID: <2024052326-popcorn-chloride-b06c@gregkh> (raw)
In-Reply-To: <20240516230151.1031190-1-opendmb@gmail.com>
On Thu, May 16, 2024 at 04:01:48PM -0700, Doug Berger wrote:
> Some registers may be modified by parallel execution contexts and
> require protections to prevent corruption.
>
> A review of the driver revealed the need for these additional
> protections.
>
> Doug Berger (3):
> net: bcmgenet: synchronize EXT_RGMII_OOB_CTRL access
> net: bcmgenet: synchronize use of bcmgenet_set_rx_mode()
> net: bcmgenet: synchronize UMAC_CMD access
>
> drivers/net/ethernet/broadcom/genet/bcmgenet.c | 14 +++++++++++++-
> drivers/net/ethernet/broadcom/genet/bcmgenet.h | 2 ++
> drivers/net/ethernet/broadcom/genet/bcmgenet_wol.c | 6 ++++++
> drivers/net/ethernet/broadcom/genet/bcmmii.c | 4 ++++
> 4 files changed, 25 insertions(+), 1 deletion(-)
>
> --
> These commits are dependent on the previously submitted:
> [PATCH stable 5.4 0/2] net: bcmgenet: revisit MAC reset
>
> 2.34.1
>
>
All now queued up, thanks.
greg k-h
prev parent reply other threads:[~2024-05-23 11:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-16 23:01 [PATCH stable 5.4 0/3] net: bcmgenet: protect contended accesses Doug Berger
2024-05-16 23:01 ` [PATCH stable 5.4 1/3] net: bcmgenet: synchronize EXT_RGMII_OOB_CTRL access Doug Berger
2024-05-16 23:01 ` [PATCH stable 5.4 2/3] net: bcmgenet: synchronize use of bcmgenet_set_rx_mode() Doug Berger
2024-05-16 23:01 ` [PATCH stable 5.4 3/3] net: bcmgenet: synchronize UMAC_CMD access Doug Berger
2024-05-23 11:31 ` Greg KH [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=2024052326-popcorn-chloride-b06c@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=davem@davemloft.net \
--cc=f.fainelli@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=opendmb@gmail.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;
as well as URLs for NNTP newsgroup(s).