[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20231117152348.GD164483@vergenet.net>
Date: Fri, 17 Nov 2023 15:23:48 +0000
From: Simon Horman <horms@...nel.org>
To: Petr Machata <petrm@...dia.com>
Cc: "David S. Miller" <davem@...emloft.net>,
Eric Dumazet <edumazet@...gle.com>,
Jakub Kicinski <kuba@...nel.org>, Paolo Abeni <pabeni@...hat.com>,
netdev@...r.kernel.org, Ido Schimmel <idosch@...dia.com>,
Amit Cohen <amcohen@...dia.com>, mlxsw@...dia.com,
Jiri Pirko <jiri@...dia.com>
Subject: Re: [PATCH net-next 04/14] devlink: Allow taking device lock in
pre_doit operations
On Wed, Nov 15, 2023 at 01:17:13PM +0100, Petr Machata wrote:
> From: Ido Schimmel <idosch@...dia.com>
>
> Introduce a new private flag ('DEVLINK_NL_FLAG_NEED_DEV_LOCK') to allow
> netlink commands to specify that they need to acquire the device lock in
> their pre_doit operation and release it in their post_doit operation.
>
> The reload command will use this flag in the subsequent patch.
>
> No functional changes intended.
>
> Signed-off-by: Ido Schimmel <idosch@...dia.com>
> Reviewed-by: Jiri Pirko <jiri@...dia.com>
> Signed-off-by: Petr Machata <petrm@...dia.com>
Reviewed-by: Simon Horman <horms@...nel.org>
...
> @@ -93,11 +95,13 @@ devlink_get_from_attrs_lock(struct net *net, struct nlattr **attrs)
> static int __devlink_nl_pre_doit(struct sk_buff *skb, struct genl_info *info,
> u8 flags)
> {
> + bool dev_lock = flags & DEVLINK_NL_FLAG_NEED_DEV_LOCK;
nit: I would have expressed the above as follows, to convert
the integer to a bool. But I understand that it makes
no difference in this case so there is no need to update the
patch for this:
bool dev_lock = !!(flags & DEVLINK_NL_FLAG_NEED_DEV_LOCK);
...
Powered by blists - more mailing lists