[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Y70jtmWJitiPxXwK@shredder>
Date: Tue, 10 Jan 2023 10:37:10 +0200
From: Ido Schimmel <idosch@...dia.com>
To: Jiri Pirko <jiri@...nulli.us>
Cc: netdev@...r.kernel.org, davem@...emloft.net, kuba@...nel.org,
pabeni@...hat.com, edumazet@...gle.com, michael.chan@...adcom.com,
yisen.zhuang@...wei.com, salil.mehta@...wei.com,
jesse.brandeburg@...el.com, anthony.l.nguyen@...el.com,
tariqt@...dia.com, saeedm@...dia.com, leon@...nel.org,
petrm@...dia.com, mailhol.vincent@...adoo.fr,
jacob.e.keller@...el.com, gal@...dia.com
Subject: Re: [patch net-next v3 04/11] devlink: protect health reporter
operation with instance lock
On Mon, Jan 09, 2023 at 07:31:13PM +0100, Jiri Pirko wrote:
> From: Jiri Pirko <jiri@...dia.com>
>
> Similar to other devlink objects, protect the reporters list
> by devlink instance lock. Alongside add unlocked versions
> of health reporter create/destroy functions and use them in drivers
> on call paths where the instance lock is held.
>
> Signed-off-by: Jiri Pirko <jiri@...dia.com>
The changes in devlink, mlxsw and netdevsim look fine to me, so:
Reviewed-by: Ido Schimmel <idosch@...dia.com>
Powered by blists - more mailing lists