netdev - Re: [PATCH] ks8842: Add module param for setting mac address

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:	Sun, 18 Apr 2010 20:50:21 +0100
From:	Ben Hutchings <bhutchings@...arflare.com>
To:	Richard Röjfors 
	<richard.rojfors@...agicore.com>
Cc:	netdev@...r.kernel.org, davem@...emloft.net
Subject: Re: [PATCH] ks8842: Add module param for setting mac address

On Sun, 2010-04-18 at 19:25 +0200, Richard Röjfors wrote:
> This patch adds a module parameter for setting the MAC address.
> 
> To ensure this MAC address is used, the MAC address is written
> after each hardware reset.
[...]

This is not an accepted way of setting the MAC address.  The accepted
ways to initialise a network controller's address are:

1. a. Controller reads it from dedicated NVRAM.  Driver reads it from
      controller.
   b. Driver reads it from dedicated NVRAM.
2. Platform firmware or boot loader passes platform data (OpenFirmware,
   device tree, etc.) to the kernel, which includes the assigned MAC
   address.  Driver uses kernel functions to read it from platform data.
3. Platform firmware or boot loader programs it into the controller.
   Driver reads it from the controller.
4. Driver generates random address.

In any case, userland can change the MAC address later.

Ben.

-- 
Ben Hutchings, Senior Software Engineer, Solarflare Communications
Not speaking for my employer; that's the marketing department's job.
They asked us to note that Solarflare product names are trademarked.

--
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