From: Heiner Kallweit <hkallweit1@gmail.com>
To: 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: Mon, 15 Jun 2020 08:20:20 +0200 [thread overview]
Message-ID: <cd26de60-493f-4c91-e411-e515a3e3f2d6@gmail.com> (raw)
In-Reply-To: <20200614232607.itigyaqamm5sql63@lion.mk-sys.cz>
On 15.06.2020 01:26, Michal Kubecek wrote:
> On Mon, Jun 15, 2020 at 12:35:30AM +0200, Heiner Kallweit wrote:
>> Seems that disabling ETHTOOL_NETLINK for PHYLIB=m has (at least) one
>> more side effect. I just saw that ifconfig doesn't report LOWER_UP
>> any longer. Reason seems to be that the ioctl fallback supports
>> 16 bits for the flags only (and IFF_LOWER_UP is bit 16).
>> See dev_ifsioc_locked().
>
> I don't think this is related to CONFIG_ETHTOOL_NETLINK; AFAIK ifconfig
> does not use netlink at all and device flags are certainly not passed
> via ethtool netlink.
>
Right, my bad. Just mixed up the output of ifconfig and "ip link",
ip link says LOWER_UP whilst ifconfig says RUNNING.
> Michal
>
Heiner
next prev parent reply other threads:[~2020-06-15 6:20 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 [this message]
2020-06-10 15:27 ` Florian Fainelli
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=cd26de60-493f-4c91-e411-e515a3e3f2d6@gmail.com \
--to=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.