From: Simon Horman <simon.horman@corigine.com>
To: Jiri Pirko <jiri@resnulli.us>
Cc: netdev@vger.kernel.org, davem@davemloft.net, kuba@kernel.org,
pabeni@redhat.com, edumazet@google.com,
michael.chan@broadcom.com, jesse.brandeburg@intel.com,
anthony.l.nguyen@intel.com, tariqt@nvidia.com, saeedm@nvidia.com,
leon@kernel.org, idosch@nvidia.com, petrm@nvidia.com,
aelior@marvell.com, manishc@marvell.com,
jacob.e.keller@intel.com, gal@nvidia.com,
yinjun.zhang@corigine.com, fei.qin@corigine.com,
Niklas.Cassel@wdc.com
Subject: Re: [patch net-next v2 09/12] devlink: protect devlink param list by instance lock
Date: Fri, 27 Jan 2023 12:41:05 +0100 [thread overview]
Message-ID: <Y9O4UUzxI1HAjVq1@corigine.com> (raw)
In-Reply-To: <Y9O2PHu7LDljh7sr@corigine.com>
On Fri, Jan 27, 2023 at 12:32:21PM +0100, Simon Horman wrote:
> On Thu, Jan 26, 2023 at 08:58:35AM +0100, Jiri Pirko wrote:
> > From: Jiri Pirko <jiri@nvidia.com>
> >
> > Commit 1d18bb1a4ddd ("devlink: allow registering parameters after
> > the instance") as the subject implies introduced possibility to register
> > devlink params even for already registered devlink instance. This is a
> > bit problematic, as the consistency or params list was originally
> > secured by the fact it is static during devlink lifetime. So in order to
> > protect the params list, take devlink instance lock during the params
> > operations. Introduce unlocked function variants and use them in drivers
> > in locked context. Put lock assertions to appropriate places.
> >
> > Signed-off-by: Jiri Pirko <jiri@nvidia.com>
> > Reviewed-by: Jakub Kicinski <kuba@kernel.org>
> > Reviewed-by: Jacob Keller <jacob.e.keller@intel.com>
> > ---
> > drivers/net/ethernet/mellanox/mlx4/main.c | 80 ++++++++--------
> > drivers/net/ethernet/mellanox/mlx5/core/dev.c | 18 ++--
> > .../net/ethernet/mellanox/mlx5/core/devlink.c | 92 +++++++++----------
> > drivers/net/ethernet/mellanox/mlx5/core/eq.c | 12 +--
> > .../net/ethernet/mellanox/mlx5/core/eswitch.c | 6 +-
> > .../net/ethernet/mellanox/mlx5/core/main.c | 12 +--
> > drivers/net/ethernet/mellanox/mlxsw/core.c | 18 ++--
> > .../net/ethernet/mellanox/mlxsw/spectrum.c | 16 ++--
> > .../ethernet/netronome/nfp/devlink_param.c | 8 +-
> > .../net/ethernet/netronome/nfp/nfp_net_main.c | 7 +-
> > drivers/net/netdevsim/dev.c | 36 ++++----
> > include/net/devlink.h | 16 +++-
> > net/devlink/leftover.c | 77 +++++++++++-----
> > 13 files changed, 218 insertions(+), 180 deletions(-)
>
> For the nfp portion:
>
> Reviewed-by: Simon Horman <simon.horman@corigine.com>
>
> I will also see about getting the patchset tested on NFP hardware.
Seems the team was a bit further ahead on the testing than I thought.
So, on their behalf:
Tested-by: Simon Horman <simon.horman@corigine.com>
next prev parent reply other threads:[~2023-01-27 11:43 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-26 7:58 [patch net-next v2 00/12] devlink: Cleanup params usage Jiri Pirko
2023-01-26 7:58 ` [patch net-next v2 01/12] net/mlx5: Change devlink param register/unregister function names Jiri Pirko
2023-01-26 7:58 ` [patch net-next v2 02/12] net/mlx5: Covert devlink params registration to use devlink_params_register/unregister() Jiri Pirko
2023-01-26 7:58 ` [patch net-next v2 03/12] devlink: make devlink_param_register/unregister static Jiri Pirko
2023-01-26 7:58 ` [patch net-next v2 04/12] devlink: don't work with possible NULL pointer in devlink_param_unregister() Jiri Pirko
2023-01-26 7:58 ` [patch net-next v2 05/12] ice: remove pointless calls to devlink_param_driverinit_value_set() Jiri Pirko
2023-01-26 7:58 ` [patch net-next v2 06/12] qed: remove pointless call " Jiri Pirko
2023-01-26 7:58 ` [patch net-next v2 07/12] devlink: make devlink_param_driverinit_value_set() return void Jiri Pirko
2023-01-26 7:58 ` [patch net-next v2 08/12] devlink: put couple of WARN_ONs in devlink_param_driverinit_value_get() Jiri Pirko
2023-01-26 7:58 ` [patch net-next v2 09/12] devlink: protect devlink param list by instance lock Jiri Pirko
2023-01-26 9:28 ` Ido Schimmel
2023-01-27 11:32 ` Simon Horman
2023-01-27 11:41 ` Simon Horman [this message]
2023-01-26 7:58 ` [patch net-next v2 10/12] net/mlx5: Move fw reset devlink param to fw reset code Jiri Pirko
2023-01-26 7:58 ` [patch net-next v2 11/12] net/mlx5: Move flow steering devlink param to flow steering code Jiri Pirko
2023-01-26 7:58 ` [patch net-next v2 12/12] net/mlx5: Move eswitch port metadata devlink param to flow eswitch code Jiri Pirko
2023-01-27 12:50 ` [patch net-next v2 00/12] devlink: Cleanup params usage 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=Y9O4UUzxI1HAjVq1@corigine.com \
--to=simon.horman@corigine.com \
--cc=Niklas.Cassel@wdc.com \
--cc=aelior@marvell.com \
--cc=anthony.l.nguyen@intel.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=fei.qin@corigine.com \
--cc=gal@nvidia.com \
--cc=idosch@nvidia.com \
--cc=jacob.e.keller@intel.com \
--cc=jesse.brandeburg@intel.com \
--cc=jiri@resnulli.us \
--cc=kuba@kernel.org \
--cc=leon@kernel.org \
--cc=manishc@marvell.com \
--cc=michael.chan@broadcom.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=petrm@nvidia.com \
--cc=saeedm@nvidia.com \
--cc=tariqt@nvidia.com \
--cc=yinjun.zhang@corigine.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