linux-kernel - Re: [PATCH v5 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] [thread-next>] [day] [month] [year] [list]

Message-Id: <20140328.172107.16072208664321602.davem@davemloft.net>
Date:	Fri, 28 Mar 2014 17:21:07 -0400 (EDT)
From:	David Miller <davem@...emloft.net>
To:	teg@...m.no
Cc:	dh.herrmann@...il.com, netdev@...r.kernel.org,
	johannes@...solutions.net, linux-wireless@...r.kernel.org,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH v5 0/4] Provide netdev naming-policy via sysfs

From: Tom Gundersen <teg@...m.no>
Date: Fri, 28 Mar 2014 21:51:53 +0100

> On Fri, Mar 28, 2014 at 7:54 PM, David Miller <davem@...emloft.net> wrote:
>> From: David Herrmann <dh.herrmann@...il.com>
>> Date: Wed, 26 Mar 2014 14:05:13 +0100
>>
>>> The main use-case is to allow udev to skip applying reliable ifnames to virtual
>>> devices. For instance, if wifi-P2P devices are created, wpas already provides a
>>> suitable naming-policy and udev shouldn't touch these devices. Same is true for
>>> other virtual devices.
>>
>> This makes no sense at all.
>>
>> If udev should avoid applying names to wifi-P2P devices, that policy can
>> be instituted completely inside of udev.  There is no need whatsoever
>> for kernel support.
>>
>> udev can look at the device type, and policies can be defined that key
>> off of that device type, entirely in userspace.
> 
> Doing this in userspace sounds really wrong and fragile.
> 
> In the case of wifi-P2P we could make it work, but for every type of
> device that is added to the kernel which is named from userspace, we
> would have to play catch-up in udev (and even after we do, new kernels
> on old userspace will never work in the expected way).

Chronically we are finding hackish ways for seperate components in
userspace to coordinate their actions.

You're right, doing this for every device type for every single attribute
that might better.... sucks.

What's really needed is generic ways for seperate userspace components
to coordinate with eachother on issues like this.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/