[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Y+UjZVPU87ISpRbn@corigine.com>
Date: Thu, 9 Feb 2023 17:46:29 +0100
From: Simon Horman <simon.horman@...igine.com>
To: Jiri Pirko <jiri@...nulli.us>
Cc: netdev@...r.kernel.org, davem@...emloft.net, kuba@...nel.org,
pabeni@...hat.com, edumazet@...gle.com, tariqt@...dia.com,
saeedm@...dia.com, jacob.e.keller@...el.com, gal@...dia.com,
kim.phillips@....com, moshe@...dia.com
Subject: Re: [patch net-next 6/7] devlink: allow to call
devl_param_driverinit_value_get() without holding instance lock
On Thu, Feb 09, 2023 at 04:43:07PM +0100, Jiri Pirko wrote:
> From: Jiri Pirko <jiri@...dia.com>
>
> If the driver maintains following basic sane behavior, the
> devl_param_driverinit_value_get() function could be called without
> holding instance lock:
>
> 1) Driver ensures a call to devl_param_driverinit_value_get() cannot
> race with registering/unregistering the parameter with
> the same parameter ID.
> 2) Driver ensures a call to devl_param_driverinit_value_get() cannot
> race with devl_param_driverinit_value_set() call with
> the same parameter ID.
> 3) Driver ensures a call to devl_param_driverinit_value_get() cannot
> race with reload operation.
>
> By the nature of params usage, these requirements should be
> trivially achievable. If the driver for some off reason
> is not able to comply, it has to take the devlink->lock while
> calling devl_param_driverinit_value_get().
>
> Remove the lock assertion and add comment describing
> the locking requirements.
>
> This fixes a splat in mlx5 driver introduced by the commit
> referenced in the "Fixes" tag.
>
> Lore: https://lore.kernel.org/netdev/719de4f0-76ac-e8b9-38a9-167ae239efc7@amd.com/
> Reported-by: Kim Phillips <kim.phillips@....com>
> Fixes: 075935f0ae0f ("devlink: protect devlink param list by instance lock")
> Signed-off-by: Jiri Pirko <jiri@...dia.com>
Reviewed-by: Simon Horman <simon.horman@...igine.com>
Powered by blists - more mailing lists