From: Stephen Hemminger <shemminger@vyatta.com>
To: Eric Dumazet <eric.dumazet@gmail.com>
Cc: David Miller <davem@davemloft.net>, netdev@vger.kernel.org
Subject: Re: RFC: netdev: allow ethtool physical id to drop rtnl_lock
Date: Fri, 30 Oct 2009 11:30:02 -0700 [thread overview]
Message-ID: <20091030113002.57357963@nehalam> (raw)
In-Reply-To: <4AEB26BB.1050007@gmail.com>
On Fri, 30 Oct 2009 18:47:39 +0100
Eric Dumazet <eric.dumazet@gmail.com> wrote:
> Stephen Hemminger a écrit :
> > The ethtool operation to blink LED can take an indeterminately long time,
> > blocking out other operations (via rtnl_lock). This patch is an attempt
> > to work around the problem.
> >
> > It does need more discussion, because it will mean that drivers that formerly
> > were protected from changes during blink aren't. For example, user could
> > start device blinking, and then plug in cable causing change netlink event
> > to change state or pull cable and have device come down.
> >
> > The other possibility is to do this on a driver by driver basis
> > which is more effort.
> >
> > Signed-off-by: Stephen Hemminger <shemminger@vyatta.com>
> >
> >
> > --- a/net/core/ethtool.c 2009-10-30 10:27:23.621917624 -0700
> > +++ b/net/core/ethtool.c 2009-10-30 10:35:53.787670774 -0700
> > @@ -17,6 +17,7 @@
> > #include <linux/errno.h>
> > #include <linux/ethtool.h>
> > #include <linux/netdevice.h>
> > +#include <linux/rtnetlink.h>
> > #include <asm/uaccess.h>
> >
> > /*
> > @@ -781,6 +782,8 @@ static int ethtool_get_strings(struct ne
> > static int ethtool_phys_id(struct net_device *dev, void __user *useraddr)
> > {
> > struct ethtool_value id;
> > + int err;
> > + static int busy;
> >
> > if (!dev->ethtool_ops->phys_id)
> > return -EOPNOTSUPP;
> > @@ -788,7 +791,21 @@ static int ethtool_phys_id(struct net_de
> > if (copy_from_user(&id, useraddr, sizeof(id)))
> > return -EFAULT;
> >
> > - return dev->ethtool_ops->phys_id(dev, id.data);
> > + if (busy)
> > + return -EBUSY;
> > +
> > + /* This operation may take a long time, drop lock */
> > + busy = 1;
> > + dev_hold(dev);
> > + rtnl_unlock();
> > +
> > + err = dev->ethtool_ops->phys_id(dev, id.data);
> > +
> > + rtnl_lock();
> > + dev_put(dev);
> > + busy = 0;
> > +
> > + return err;
> > }
> >
>
> It seems reasonable, but why have a global 'busy' flag, and not
> private to each netdev ?
>
Because that is what old behaviour was (one blink at a time).
--
next prev parent reply other threads:[~2009-10-30 18:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-30 17:42 RFC: netdev: allow ethtool physical id to drop rtnl_lock Stephen Hemminger
2009-10-30 17:47 ` Eric Dumazet
2009-10-30 18:30 ` Stephen Hemminger [this message]
2009-10-31 16:44 ` Michael Chan
2009-11-02 8:17 ` David Miller
2009-11-02 16:51 ` Stephen Hemminger
2009-11-02 18:29 ` Ben Hutchings
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=20091030113002.57357963@nehalam \
--to=shemminger@vyatta.com \
--cc=davem@davemloft.net \
--cc=eric.dumazet@gmail.com \
--cc=netdev@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).