netdev - Re: wilc1000 MAC address is 00:00:00:00:00:00

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:   Thu, 9 Feb 2023 13:07:25 -0800
From:   Jakub Kicinski <kuba@...nel.org>
To:     <Ajay.Kathat@...rochip.com>
Cc:     <heiko.thiery@...il.com>, <Claudiu.Beznea@...rochip.com>,
        <kvalo@...nel.org>, <linux-wireless@...r.kernel.org>,
        <michael@...le.cc>, <netdev@...r.kernel.org>,
        <Amisha.Patel@...rochip.com>
Subject: Re: wilc1000 MAC address is 00:00:00:00:00:00

On Thu, 9 Feb 2023 18:51:58 +0000 Ajay.Kathat@...rochip.com wrote:
> > netdev should be created with a valid lladdr, is there something
> > wifi-specific here that'd prevalent that? The canonical flow is
> > to this before registering the netdev:
> 
> Here it's the timing in wilc1000 by when the MAC address is available to
> read from NV. NV read is available in "mac_open" net_device_ops instead
> of bus probe function. I think, mostly the operations on netdev which
> make use of mac address are performed after the "mac_open" (I may be
> missing something).
> 
> Does it make sense to assign a random address in probe and later read
> back from NV in mac_open to make use of stored value?

Hard to say, I'd suspect that may be even more confusing than
starting with zeroes. There aren't any hard rules around the
addresses AFAIK, but addrs are visible to user space. So user
space will likely make assumptions based on the most commonly 
observed sequence (reading real addr at probe).