mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Justin Chen <justin.chen@broadcom.com>
To: Simon Horman <simon.horman@corigine.com>
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
	davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
	pabeni@redhat.com, bcm-kernel-feedback-list@broadcom.com,
	florian.fainelli@broadcom.com,
	Daniil Tatianin <d-tatianin@yandex-team.ru>,
	Andrew Lunn <andrew@lunn.ch>
Subject: Re: [PATCH net-next] ethtool: ioctl: improve error checking for set_wol
Date: Thu, 1 Jun 2023 09:22:50 -0700	[thread overview]
Message-ID: <e7e49753-3ad6-9e03-44ff-945e66fca9a3@broadcom.com> (raw)
In-Reply-To: <ZHi/aT6vxpdOryD8@corigine.com>

[-- Attachment #1: Type: text/plain, Size: 2278 bytes --]



On 6/1/2023 8:55 AM, Simon Horman wrote:
> + Daniil Tatianin <d-tatianin@yandex-team.ru>, Andrew Lunn <andrew@lunn.ch>
>    as per ./scripts/get_maintainer.pl --git-min-percent 25 net/ethtool/ioctl.c
> 
> On Wed, May 31, 2023 at 01:53:49PM -0700, Justin Chen wrote:
>> The netlink version of set_wol checks for not supported wolopts and avoids
>> setting wol when the correct wolopt is already set. If we do the same with
>> the ioctl version then we can remove these checks from the driver layer.
> 
> Hi Justin,
> 
> Are you planning follow-up patches for the driver layer?
> 

I was planning to for the Broadcom drivers since those I can test. But I 
could do it across the board if that is preferred.

>> Signed-off-by: Justin Chen <justin.chen@broadcom.com>
>> ---
>>   net/ethtool/ioctl.c | 14 ++++++++++++--
>>   1 file changed, 12 insertions(+), 2 deletions(-)
>>
>> diff --git a/net/ethtool/ioctl.c b/net/ethtool/ioctl.c
>> index 6bb778e10461..80f456f83db0 100644
>> --- a/net/ethtool/ioctl.c
>> +++ b/net/ethtool/ioctl.c
>> @@ -1436,15 +1436,25 @@ static int ethtool_get_wol(struct net_device *dev, char __user *useraddr)
>>   
>>   static int ethtool_set_wol(struct net_device *dev, char __user *useraddr)
>>   {
>> -	struct ethtool_wolinfo wol;
>> +	struct ethtool_wolinfo wol, cur_wol;
>>   	int ret;
>>   
>> -	if (!dev->ethtool_ops->set_wol)
>> +	if (!dev->ethtool_ops->get_wol || !dev->ethtool_ops->set_wol)
>>   		return -EOPNOTSUPP;
> 
> Are there cases where (in-tree) drivers provide set_wol byt not get_wol?
> If so, does this break their set_wol support?
> 

My original thought was to match netlink set wol behavior. So drivers 
that do that won't work with netlink set_wol right now. I'll skim around 
to see if any drivers do this. But I would reckon this should be a 
driver fix.

Thanks,
Justin

>>   
>> +	memset(&cur_wol, 0, sizeof(struct ethtool_wolinfo));
>> +	cur_wol.cmd = ETHTOOL_GWOL;
>> +	dev->ethtool_ops->get_wol(dev, &cur_wol);
>> +
>>   	if (copy_from_user(&wol, useraddr, sizeof(wol)))
>>   		return -EFAULT;
>>   
>> +	if (wol.wolopts & ~cur_wol.supported)
>> +		return -EOPNOTSUPP;
>> +
>> +	if (wol.wolopts == cur_wol.wolopts)
>> +		return 0;
>> +
>>   	ret = dev->ethtool_ops->set_wol(dev, &wol);
>>   	if (ret)
>>   		return ret;

[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 4206 bytes --]

  parent reply	other threads:[~2023-06-01 16:23 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1685566429-2869-1-git-send-email-justin.chen@broadcom.com>
2023-06-01 15:55 ` Simon Horman
2023-06-01 16:03   ` Jakub Kicinski
2023-06-01 16:23     ` Simon Horman
2023-06-01 16:23     ` Justin Chen
2023-06-01 16:22   ` Justin Chen [this message]
2023-06-01 18:27     ` Justin Chen
2023-06-01 18:37       ` Florian Fainelli
2023-06-01 18:48         ` Andrew Lunn
2023-06-01 18:58           ` Justin Chen
2023-06-01 20:41             ` Woojung.Huh
2023-06-02  8:54     ` Simon Horman
2023-06-05 18:21 ` Jakub Kicinski
2023-06-05 18:46 Justin Chen
2023-06-07  3:54 ` Jakub Kicinski

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=e7e49753-3ad6-9e03-44ff-945e66fca9a3@broadcom.com \
    --to=justin.chen@broadcom.com \
    --cc=andrew@lunn.ch \
    --cc=bcm-kernel-feedback-list@broadcom.com \
    --cc=d-tatianin@yandex-team.ru \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=florian.fainelli@broadcom.com \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=simon.horman@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

all inboxes | Powered by JetHome®