linux-kernel - Re: new sysfs layout and ethernet device names

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Thu, 22 Mar 2007 09:47:34 +0100
From:	"Kay Sievers" <kay.sievers@...y.org>
To:	"Bill Nottingham" <notting@...hat.com>
Cc:	linux-kernel@...r.kernel.org, "Greg KH" <greg@...ah.com>
Subject: Re: new sysfs layout and ethernet device names

On 3/20/07, Bill Nottingham <notting@...hat.com> wrote:
> I was fiddling with the 'new' (no CONFIG_SYSFS_DEPRECATED) layout
> and ethernet device names, and noticed that the new layout effectively
> restricts the availability of certain device names.
>
> By making a directory for the ethernet device name in the parent
> device, you no longer can use any name that is used in sysfs for
> the parent device type - for PCI devices this would be 'resource0',
> 'power', 'enable', etc. For USB, it would be a different set
> of names that are no longer available.

Yeah, we heard, people want to name their network interfaces "irq". :)

> If you *do* try to use one of these names, the rename will succeed...
> partway. The link in /sys/class/net is renamed, the directory is
> not (as it obviously can't rename on top of whatever is already there.)
> Various networking tools then break in assorted ways due to the
> naming disconnect.
>
> Going back to the deprecated layout makes these names available again -
> it's possible (although not necessarily likely) that the new layout
> will break someone's device configuration if they upgrade kernels,
> even if the rest of their tools are updated for the new layout.

There will be a directory at the bus-device with the name of the
class, that glues together the bus-devices and the class-devices in
the unified tree:
  http://git.kernel.org/?p=linux/kernel/git/gregkh/patches.git;a=blob;f=driver/driver-core-fix-namespace-issue-with-devices-assigned-to-classes.patch;hb=HEAD

So the network-interface(s) will be in their own directory "net",
below the bus-device, and don't conflict with the existing attributes.

Thanks,
Kay
-
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/