All of lore.kernel.org
 help / color / mirror / Atom feed
From: Florian Fainelli <f.fainelli@gmail.com>
To: Heiner Kallweit <hkallweit1@gmail.com>,
	Michal Kubecek <mkubecek@suse.cz>
Cc: "netdev@vger.kernel.org" <netdev@vger.kernel.org>
Subject: Re: ethtool 5.7: netlink ENOENT error when setting WOL
Date: Wed, 10 Jun 2020 08:27:10 -0700	[thread overview]
Message-ID: <0353ce74-ffc6-4d40-bf0f-d2a7ad640b30@gmail.com> (raw)
In-Reply-To: <a433a0b0-bf5e-ad90-8373-4f88e2ef991d@gmail.com>



On 6/10/2020 3:50 AM, Heiner Kallweit wrote:
> On 10.06.2020 11:13, Michal Kubecek wrote:
>> On Wed, Jun 10, 2020 at 10:52:26AM +0200, Heiner Kallweit wrote:
>>> On 10.06.2020 10:26, Heiner Kallweit wrote:
>>>> Since ethtool 5.7 following happens (kernel is latest linux-next):
>>>>
>>>> ethtool -s enp3s0 wol g
>>>> netlink error: No such file or directory
>>>>
>>>> With ethtool 5.6 this doesn't happen. I also checked the latest ethtool
>>>> git version (5.7 + some fixes), error still occurs.
>>>>
>>>> Heiner
>>>>
>>> Bisecting points to:
>>> netlink: show netlink error even without extack
>>
>> Just to make sure you are hitting the same problem I'm just looking at,
>> please check if
>>
>> - your kernel is built with ETHTOOL_NETLINK=n
> 
> No, because I have PHYLIB=m.
> Not sure what it would take to allow building ethtool netlink support
> as a module. But that's just on a side note.

Not sure it makes sense to build ETHTOOL_NETLINK as a module, but at
least ensuring that ETHTOOL_NETLINK is built into the kernel if PHYLIB=y
or PHYLIB=m would make sense, or, better we find a way to decouple the
two by using function pointers from the phy_driver directly that way
there is no symbol dependency (but reference counting has to work).
-- 
Florian

  parent reply	other threads:[~2020-06-10 15:27 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-10  8:26 ethtool 5.7: netlink ENOENT error when setting WOL Heiner Kallweit
2020-06-10  8:52 ` Heiner Kallweit
2020-06-10  9:13   ` Michal Kubecek
2020-06-10 10:50     ` Heiner Kallweit
2020-06-10 11:53       ` Michal Kubecek
2020-06-14 22:35         ` Heiner Kallweit
2020-06-14 23:26           ` Michal Kubecek
2020-06-15  6:20             ` Heiner Kallweit
2020-06-10 15:27       ` Florian Fainelli [this message]
2020-06-10 20:05         ` Andrew Lunn
2020-06-14 16:14           ` Heiner Kallweit
2020-06-14 16:44             ` Florian Fainelli

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=0353ce74-ffc6-4d40-bf0f-d2a7ad640b30@gmail.com \
    --to=f.fainelli@gmail.com \
    --cc=hkallweit1@gmail.com \
    --cc=mkubecek@suse.cz \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.