netdev - Re: [PATCH] via-velocity: earlier name allocation

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: <490027DE.3000409@svenhartge.de>
Date:	Thu, 23 Oct 2008 09:29:34 +0200
From:	Sven Hartge <sven@...nhartge.de>
To:	Stephen Hemminger <shemminger@...tta.com>
CC:	netdev@...r.kernel.org
Subject: Re: [PATCH] via-velocity: earlier name allocation

Stephen Hemminger wrote:


> NAK
> 
> There is nothing to prevent that device name from being allocated by another device
> at that point.  The correct fix is to not use dev->name until after registering
> the network device.  Change the order of registration or pass dev_driver_string(&pdev->dev)
> instead of dev->name to velocity_get_options

Fine with me. This was just the hint I was looking for. If you don't
mind, I will mail a new patch for this case later.

S°

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