[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <d016b1dc-c8ee-9826-57e8-1edc7a09a515@intel.com>
Date: Wed, 18 Jan 2023 13:17:59 -0800
From: Jacob Keller <jacob.e.keller@...el.com>
To: Jiri Pirko <jiri@...nulli.us>, <netdev@...r.kernel.org>
CC: <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>,
<idosch@...dia.com>, <petrm@...dia.com>,
<mailhol.vincent@...adoo.fr>, <gal@...dia.com>
Subject: Re: [patch net-next v5 05/12] devlink: protect health reporter
operation with instance lock
On 1/18/2023 7:21 AM, 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.
>
Reviewed-by: Jacob Keller <jacob.e.keller@...el.com>
Powered by blists - more mailing lists