[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20090106082928.GB19690@localhost>
Date: Tue, 6 Jan 2009 16:29:28 +0800
From: Wu Fengguang <wfg@...ux.intel.com>
To: Peter Korsgaard <jacmet@...site.dk>
Cc: netdev@...r.kernel.org
Subject: Re: [PATCH] dm9601: handle corrupt mac address
Hi Peter,
On Tue, Jan 06, 2009 at 09:04:58AM +0100, Peter Korsgaard wrote:
> >>>>> "Wu" == Wu Fengguang <wfg@...ux.intel.com> writes:
>
> Wu> Some cheap devices ship with dangling EEPROM pins!
> Wu> They always return invalid address ff:ff:ff:ff:ff:ff.
>
> Wu> Inherit the auto-generated address in this case,
> Wu> so that these products can work with zero configuration.
>
> Wu> Signed-off-by: Wu Fengguang <fengguang.wu@...el.com>
>
> Wu> + /*
> Wu> + * Overwrite the auto-generated address only with good ones.
> Wu> + */
> Wu> + if (is_valid_ether_addr(mac))
> Wu> + memcpy(dev->net->dev_addr, mac, ETH_ALEN);
> Wu> +
>
> Do we automatically get a random address in netdev nowadays without
> calling random_ether_addr? I didn't know that.
I confirmed based on both code review and tests.
The logic goes like this in usbnet.c:
80 // randomly generated ethernet address
81 static u8 node_id [ETH_ALEN];
...
1118 int
1119 usbnet_probe (struct usb_interface *udev, const struct usb_device_id *prod)
1120 {
...
1168 dev->net = net;
1169 strcpy (net->name, "usb%d");
1170 memcpy (net->dev_addr, node_id, sizeof node_id);
...
1192 // allow device-specific bind/init procedures
1193 // NOTE net->name still not usable ...
1194 if (info->bind) {
1195 status = info->bind (dev, udev);
> Anyway, I would prefer to add a dev_warn mentioning the fact that
> we're using a random address (and which one).
I'll do that in another patch. Since I'd like to add one more similar
warning to dm9601_set_mac_address(). That warning helped me identify
this bug.
> Other than that,
>
> Signed-off-by: Peter Korsgaard <jacmet@...site.dk>
Thanks,
Fengguang
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists