netdev - Re: [patch net-next 0/2] net: init perm

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] [day] [month] [year] [list]

Message-Id: <20130108.180106.1572147969019302833.davem@davemloft.net>
Date:	Tue, 08 Jan 2013 18:01:06 -0800 (PST)
From:	David Miller <davem@...emloft.net>
To:	jiri@...nulli.us
Cc:	netdev@...r.kernel.org, edumazet@...gle.com,
	bhutchings@...arflare.com, shemminger@...tta.com,
	ebiederm@...ssion.com, amwang@...hat.com, sassmann@...hat.com
Subject: Re: [patch net-next 0/2] net: init perm_addr properly and on one
 place

From: Jiri Pirko <jiri@...nulli.us>
Date: Tue,  8 Jan 2013 12:38:24 +0100

> So far, it has been driver's responsibility to initialize ->perm_addr. Many
> of them does not do that though. So benefit from ->addr_assign_type existence
> and in case the type is NET_ADDR_PERM, set the ->perm_addr during dev register
> process. That allows to remove most of the driver's initializations (that what
> happen before register_netdevice() call).
> 
> Jiri Pirko (2):
>   net: init perm_addr in register_netdevice()
>   remove init of dev->perm_addr in drivers

Nice cleanup, all applied, thanks!
--
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