netdev - Re: [patch net-next v2 4/7] switchdev: introduce possibility to defer obj

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <561BC4F1.5080005@cumulusnetworks.com>
Date:	Mon, 12 Oct 2015 16:34:25 +0200
From:	Nikolay Aleksandrov <nikolay@...ulusnetworks.com>
To:	Jiri Pirko <jiri@...nulli.us>, netdev@...r.kernel.org
Cc:	davem@...emloft.net, idosch@...lanox.com, eladr@...lanox.com,
	sfeldma@...il.com, f.fainelli@...il.com, linux@...ck-us.net,
	vivien.didelot@...oirfairelinux.com, andrew@...n.ch,
	john.fastabend@...il.com, David.Laight@...LAB.COM,
	stephen@...workplumber.org
Subject: Re: [patch net-next v2 4/7] switchdev: introduce possibility to defer
 obj_add/del

On 10/12/2015 03:15 PM, Jiri Pirko wrote:
> From: Jiri Pirko <jiri@...lanox.com>
> 
> Similar to the attr usecase, the caller knows if he is holding RTNL and is
> in atomic section. So let the called to decide the correct call variant.
> 
> This allows drivers to sleep inside their ops and wait for hw to get the
> operation status. Then the status is propagated into switchdev core.
> This avoids silent errors in drivers.
> 
> Signed-off-by: Jiri Pirko <jiri@...lanox.com>
> ---
>  include/net/switchdev.h   |   1 +
>  net/switchdev/switchdev.c | 137 +++++++++++++++++++++++++++++++++++++---------
>  2 files changed, 112 insertions(+), 26 deletions(-)
> 
[snip]
> +
> +struct switchdev_obj_work {
> +	struct work_struct work;
> +	struct net_device *dev;
> +	struct switchdev_obj obj;
> +	bool add; /* add of del */
s/of/or/ ? :-)

> +};
> +
> +static void switchdev_port_obj_work(struct work_struct *work)
> +{
> +	struct switchdev_obj_work *ow =
> +			container_of(work, struct switchdev_obj_work, work);
> +	bool rtnl_locked = rtnl_is_locked();
> +	int err;
> +
> +	if (!rtnl_locked)
> +		rtnl_lock();
> +	if (ow->add)
> +		err = switchdev_port_obj_add_now(ow->dev, &ow->obj);
> +	else
> +		err = switchdev_port_obj_del_now(ow->dev, &ow->obj);
> +	if (err && err != -EOPNOTSUPP)
> +		netdev_err(ow->dev, "failed (err=%d) to %s object (id=%d)\n",
> +			   err, ow->add ? "add" : "del", ow->obj.id);
> +	if (!rtnl_locked)
> +		rtnl_unlock();
> +
> +	dev_put(ow->dev);
> +	kfree(ow);
> +}
> +
> +static int switchdev_port_obj_work_schedule(struct net_device *dev,
> +					    const struct switchdev_obj *obj,
> +					    bool add)
> +{
> +	struct switchdev_obj_work *ow;
> +
> +	ow = kmalloc(sizeof(*ow), GFP_ATOMIC);
> +	if (!ow)
> +		return -ENOMEM;
> +
> +	INIT_WORK(&ow->work, switchdev_port_obj_work);
> +
This can be called without rtnl, what stops the device from disappearing
between the above and the hold below ?

> +	dev_hold(dev);
> +	ow->dev = dev;
> +	memcpy(&ow->obj, obj, sizeof(ow->obj));
> +	ow->add = add;
> +
> +	queue_work(switchdev_wq, &ow->work);
> +	return 0;
> +}
> +
[snip]

--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html