From: Vladimir Oltean <vladimir.oltean@nxp.com>
To: Horatiu Vultur <horatiu.vultur@microchip.com>
Cc: "netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"UNGLinuxDriver@microchip.com" <UNGLinuxDriver@microchip.com>,
"davem@davemloft.net" <davem@davemloft.net>,
"edumazet@google.com" <edumazet@google.com>,
"kuba@kernel.org" <kuba@kernel.org>,
"pabeni@redhat.com" <pabeni@redhat.com>
Subject: Re: [PATCH net 0/5] net: lan966x: Fix issues with MAC table
Date: Sat, 16 Jul 2022 20:10:45 +0000 [thread overview]
Message-ID: <20220716201043.ps6z4mxlagluwtyw@skbuf> (raw)
In-Reply-To: <20220714194040.231651-1-horatiu.vultur@microchip.com>
On Thu, Jul 14, 2022 at 09:40:35PM +0200, Horatiu Vultur wrote:
> The patch series fixes 2 issues:
> - when an entry was forgotten the irq thread was holding a spin lock and then
> was talking also rtnl_lock.
> - the access to the HW MAC table is indirect, so the access to the HW MAC
> table was not synchronized, which means that there could be race conditions.
Reviewed-by: Vladimir Oltean <vladimir.oltean@nxp.com>
next prev parent reply other threads:[~2022-07-16 20:10 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-14 19:40 [PATCH net 0/5] net: lan966x: Fix issues with MAC table Horatiu Vultur
2022-07-14 19:40 ` [PATCH net 1/5] net: lan966x: Fix taking rtnl_lock while holding spin_lock Horatiu Vultur
2022-07-14 19:40 ` [PATCH net 2/5] net: lan966x: Fix usage of lan966x->mac_lock when entry is added Horatiu Vultur
2022-07-14 19:40 ` [PATCH net 3/5] net: lan966x: Fix usage of lan966x->mac_lock when entry is removed Horatiu Vultur
2022-07-14 19:40 ` [PATCH net 4/5] net: lan966x: Fix usage of lan966x->mac_lock inside lan966x_mac_irq_handler Horatiu Vultur
2022-07-14 19:40 ` [PATCH net 5/5] net: lan966x: Fix usage of lan966x->mac_lock when used by FDB Horatiu Vultur
2022-07-16 20:10 ` Vladimir Oltean [this message]
2022-07-19 3:20 ` [PATCH net 0/5] net: lan966x: Fix issues with MAC table patchwork-bot+netdevbpf
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=20220716201043.ps6z4mxlagluwtyw@skbuf \
--to=vladimir.oltean@nxp.com \
--cc=UNGLinuxDriver@microchip.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horatiu.vultur@microchip.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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