linux-kernel - RE: [v3] wlcore: add missing nvs file name info for wilink8

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]

Message-ID: <8665E2433BC68541A24DFFCA87B70F5B3640DDC7@DFRE01.ent.ti.com>
Date:   Tue, 25 Jul 2017 11:32:28 +0000
From:   "Reizer, Eyal" <eyalr@...com>
To:     Tony Lindgren <tony@...mide.com>
CC:     Kalle Valo <kvalo@...eaurora.org>,
        "linux-wireless@...r.kernel.org" <linux-wireless@...r.kernel.org>,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
        "sebastian.reichel@...labora.co.uk" 
        <sebastian.reichel@...labora.co.uk>
Subject: RE: [v3] wlcore: add missing nvs file name info for wilink8



> -----Original Message-----
> From: Tony Lindgren [mailto:tony@...mide.com]
> Sent: Tuesday, July 25, 2017 1:22 PM
> To: Reizer, Eyal
> Cc: Kalle Valo; linux-wireless@...r.kernel.org; linux-kernel@...r.kernel.org;
> sebastian.reichel@...labora.co.uk
> Subject: Re: [v3] wlcore: add missing nvs file name info for wilink8
> 
> * Reizer, Eyal <eyalr@...com> [170720 05:17]:
> > The following commits:
> > c815fde wlcore: spi: Populate config firmware data
> > d776fc8 wlcore: sdio: Populate config firmware data
> >
> > Populated the nvs entry for wilink6 and wilink7 only while it is
> > still needed for wilink8 as well.
> > This broke user space backward compatibility when upgrading from older
> > kernels, as the alternate mac address would not be read from the nvs that is
> > already present in the file system (lib/firmware/ti-connectivity/wl1271-
> nvs.bin)
> > causing mac address change of the wlan interface.
> >
> > This patch fix this and update the structure field with the same default nvs
> file
> > name that has been used before.
> >
> > In addition, some distros hold a default wl1271-nvs.bin in the file
> > system with a bogus mac address (deadbeef...) that for a wl18xx device
> > also overrides the mac address that is stored inside the device.
> > Warn users about this bogus mac address.
> >
> > Cc: stable <stable@...r.kernel.org>
> > Signed-off-by: Eyal Reizer <eyalr@...com>
> > ---
> > v2->v3: add a check for default deadbeef... mac address and warn about it
> >
> >  drivers/net/wireless/ti/wlcore/main.c | 10 ++++++++++
> >  drivers/net/wireless/ti/wlcore/sdio.c |  1 +
> >  drivers/net/wireless/ti/wlcore/spi.c  |  1 +
> >  3 files changed, 12 insertions(+)
> >
> > diff --git a/drivers/net/wireless/ti/wlcore/main.c
> b/drivers/net/wireless/ti/wlcore/main.c
> > index 60aaa85..37c35aa 100644
> > --- a/drivers/net/wireless/ti/wlcore/main.c
> > +++ b/drivers/net/wireless/ti/wlcore/main.c
> > @@ -5961,6 +5961,16 @@ static void wl12xx_derive_mac_addresses(struct
> wl1271 *wl, u32 oui, u32 nic)
> >  	if (nic + WLCORE_NUM_MAC_ADDRESSES - wl->num_mac_addr >
> 0xffffff)
> >  		wl1271_warning("NIC part of the MAC address wraps
> around!");
> >
> > +	if (oui == 0xdeadbe && nic == 0xef0000)
> > +		wl1271_warning("Detected unconfigured mac address in
> nvs.\n"
> > +				"in case of using a wl12xx device, your "
> > +				"device performance may not be optimized.\n"
> > +				"Please use the calibrator tool to configure "
> > +				"your device.\n"
> > +				"When using a wl18xx device the nvs file can "
> > +				"be removed as a default mac address is "
> > +				"stored internally.\n");
> > +
> >  	for (i = 0; i < wl->num_mac_addr; i++) {
> >  		wl->addresses[i].addr[0] = (u8)(oui >> 16);
> >  		wl->addresses[i].addr[1] = (u8)(oui >> 8);
> 
> Hmm so why would we ever even use this bogus nvs file? In addition to
> warning,
> I think we should just ignore the bogus nvs file completely.
> 
While it looks bogus, it is still at least a valid mac address and the chip will function
Using it.
Wilink6/7 doesn't have a  default mac address in hardware (wilink8 does have one)
so we need to assign one for it so It can work, even if not optimally until configured 
using the calibrator tool and a unique mac address is assigned to it.

Best Regards,
Eyal