From: Justin Chen <justin.chen@broadcom.com>
To: Andrew Lunn <andrew@lunn.ch>
Cc: netdev@vger.kernel.org, bcm-kernel-feedback-list@broadcom.com,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Daniil Tatianin <d-tatianin@yandex-team.ru>,
Marco Bonelli <marco@mebeim.net>,
Vincent Mailhol <mailhol.vincent@wanadoo.fr>,
Maxim Korotkov <korotkov.maxim.s@gmail.com>,
Gal Pressman <gal@nvidia.com>, Jiri Pirko <jiri@resnulli.us>,
Kuniyuki Iwashima <kuniyu@amazon.com>,
Simon Horman <simon.horman@corigine.com>,
Florian Fainelli <florian.fainelli@broadcom.com>,
open list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH net-next] ethtool: ioctl: account for sopass diff in set_wol
Date: Mon, 12 Jun 2023 16:00:01 -0700 [thread overview]
Message-ID: <c0220ac1-147f-6521-a463-1d7c3e126661@broadcom.com> (raw)
In-Reply-To: <9ec8eac3-6b2f-4455-89ef-2d5768b4cee9@lunn.ch>
[-- Attachment #1: Type: text/plain, Size: 1164 bytes --]
On 6/12/23 3:28 PM, Andrew Lunn wrote:
> On Mon, Jun 12, 2023 at 02:37:00PM -0700, Justin Chen wrote:
>> sopass won't be set if wolopt doesn't change. This means the following
>> will fail to set the correct sopass.
>> ethtool -s eth0 wol s sopass 11:22:33:44:55:66
>> ethtool -s eth0 wol s sopass 22:44:55:66:77:88
>>
>> Make sure we call into the driver layer set_wol if sopass is different.
>>
>> Fixes: 55b24334c0f2 ("ethtool: ioctl: improve error checking for set_wol")
>> Signed-off-by: Justin Chen <justin.chen@broadcom.com>
>> ---
>>
>> Note: Tagged "Fixes" patch has not hit rc yet.
>>
>> net/ethtool/ioctl.c | 3 ++-
>
> Hi Justin
>
> Does the netlink version get this correct?
>
Yup netlink gets this correct
> And just for my own curiosity, why are you so interested in the ioctl
> version, which is deprecated and not used by modern versions of
> ethtool?
>
No particular reason. I was working on another driver and was planning
to remove the set_wol error checking in the driver layer when I realized
netlink set_wol was already doing it. Then on further inspection I
noticed the ioctl version doesn't do the same thing.
Justin
> Andrew
[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 4206 bytes --]
next prev parent reply other threads:[~2023-06-12 23:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-12 21:37 Justin Chen
2023-06-12 22:28 ` Andrew Lunn
2023-06-12 23:00 ` Justin Chen [this message]
2023-06-14 5:10 ` patchwork-bot+netdevbpf
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=c0220ac1-147f-6521-a463-1d7c3e126661@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=gal@nvidia.com \
--cc=jiri@resnulli.us \
--cc=korotkov.maxim.s@gmail.com \
--cc=kuba@kernel.org \
--cc=kuniyu@amazon.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mailhol.vincent@wanadoo.fr \
--cc=marco@mebeim.net \
--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®