netdev - Re: [PATCH v6 0/4] Provide netdev naming-policy via sysfs

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: <20140403.140324.1744832114380351572.davem@davemloft.net>
Date:	Thu, 03 Apr 2014 14:03:24 -0400 (EDT)
From:	David Miller <davem@...emloft.net>
To:	dh.herrmann@...il.com
Cc:	netdev@...r.kernel.org, teg@...m.no, johannes@...solutions.net,
	linux-wireless@...r.kernel.org, linux-kernel@...r.kernel.org,
	kay.sievers@...y.org
Subject: Re: [PATCH v6 0/4] Provide netdev naming-policy via sysfs

From: David Herrmann <dh.herrmann@...il.com>
Date: Wed,  2 Apr 2014 11:58:22 +0200

> This is v6 of the name_assign_type attribute for netdevs. Changes since v5 [1]:
>  - Acked-by: Kay Sievers
>  - rebased on net-next of today
> 
> Aimed for 3.15, but feel free to delay for 3.16 if you want it in -next for some
> more time.

I'm fine with the basic idea, but the implementation needs work and
this will be deferred to 3.16 in any event.

We really need to specify the name allocation type at alloc_netdev()
time, I know that's more work but that's the only way you can be sure
you caught all such cases.

I know you missed the ISDN layer, where the name can come from the
user via an ioctl().  I'm sure there were several more.

You can even do something like make alloc_netdev_enumerated()
be a shorthand for alloc_netdev(size, name, NET_NAME_ENUM, ...)

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