From: Ben Hutchings <bhutchings@solarflare.com>
To: "Michał Mirosław" <mirq-linux@rere.qmqm.pl>
Cc: <netdev@vger.kernel.org>
Subject: Re: ethtool: allow ETHTOOL_GSSET_INFO for users
Date: Mon, 23 Jan 2012 01:19:17 +0000 [thread overview]
Message-ID: <1327281557.8004.137.camel@deadeye> (raw)
In-Reply-To: <197ddc79ac33a67c56b42a226af3f30056bceb5c.1327227549.git.mirq-linux@rere.qmqm.pl>
On Sun, 2012-01-22 at 11:20 +0100, Michał Mirosław wrote:
> Allow ETHTOOL_GSSET_INFO ethtool ioctl() for unprivileged users.
> ETHTOOL_GSTRINGS is already allowed, but is unusable without this one.
>
> Signed-off-by: Michał Mirosław <mirq-linux@rere.qmqm.pl>
Acked-by: Ben Hutchings <bhutchings@solarflare.com>
We should probably also add:
ETHTOOL_GLINK
ETHTOOL_GRXFHINDIR
ETHTOOL_GCHANNELS
Ben.
> ---
> net/core/ethtool.c | 1 +
> 1 files changed, 1 insertions(+), 0 deletions(-)
>
> [against net, but probably suitable for stable, too]
>
> diff --git a/net/core/ethtool.c b/net/core/ethtool.c
> index 921aa2b..369b418 100644
> --- a/net/core/ethtool.c
> +++ b/net/core/ethtool.c
> @@ -1311,6 +1311,7 @@ int dev_ethtool(struct net *net, struct ifreq *ifr)
> case ETHTOOL_GRXCSUM:
> case ETHTOOL_GTXCSUM:
> case ETHTOOL_GSG:
> + case ETHTOOL_GSSET_INFO:
> case ETHTOOL_GSTRINGS:
> case ETHTOOL_GTSO:
> case ETHTOOL_GPERMADDR:
--
Ben Hutchings, Staff Engineer, Solarflare
Not speaking for my employer; that's the marketing department's job.
They asked us to note that Solarflare product names are trademarked.
next prev parent reply other threads:[~2012-01-23 1:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-22 10:20 ethtool: allow ETHTOOL_GSSET_INFO for users Michał Mirosław
2012-01-23 1:19 ` Ben Hutchings [this message]
2012-01-23 4:41 ` David Miller
-- strict thread matches above, loose matches on Subject: below --
2012-06-12 23:27 Ben Hutchings
2012-06-13 4:33 ` David Miller
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=1327281557.8004.137.camel@deadeye \
--to=bhutchings@solarflare.com \
--cc=mirq-linux@rere.qmqm.pl \
--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).