netdev - Re: network interface *name* alias support?

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: <alpine.LNX.1.10.0805272330170.12937@fbirervta.pbzchgretzou.qr>
Date:	Tue, 27 May 2008 23:49:03 +0200 (CEST)
From:	Jan Engelhardt <jengelh@...ozas.de>
To:	Matt Domsch <Matt_Domsch@...l.com>
cc:	David Miller <davem@...emloft.net>, kaber@...sh.net,
	dwmw2@...radead.org, jchapman@...alix.com, jonathan@...masters.org,
	tgraf@...g.ch, rick.jones2@...com, auke-jan.h.kok@...el.com,
	johnathan@...masters.org, netdev@...r.kernel.org
Subject: Re: network interface *name* alias support?

On Tuesday 2008-05-27 21:03, Matt Domsch wrote:
>
>OK, I'm just trying to understand how you would see this "feature"
>being implemented in userspace.  Advice welcome.
>
>I keep looking at my analogue: disk devices.
>Disks have a hard-coded association: Some device node with number
>(8,0) means "the first SCSI disk device" to the kernel.  Regardless of
>what the name of the file that implements the device node is (probably
>/dev/sda, but not necessarily), or if there are symlinks pointing at
>that file.  The kernel only cares about the linkage between the device
>node and the driver that accepts read/write/ioctl/etc. to it.
>
>Network devices have no such thing that I can tell.  I get at the
>device names (as presently assigned) by reading /proc/net/dev (I'd be
>happy to be told of a more correct way - this is what net-tools uses.)
>[...]
>Something like that?

The "correct" way seems to be sending off netlink messages (look at
the iproute2 code -- if you dare), or for shell scripts perhaps just
globbing up /sys/class/net/*.

And that's probably where it already ends. I like your analogy to
disk devices: the kernel keeps exactly one association (namely,
kdev_t to the device driver), so it seems sane to do the same for
network devices.

Make a /dev/net directory, and let udev populate it with symlinks in
the fashion of "bus-pci-0000:02.9 -> eth0". Note the potential
symlink loop, which should be of no concern since readlink(2)
dereferences it exactly once.

The catch: you cannot use "bus-pci-0000:02.9" as a device name
when directly talking to the kernel, it needs to be resolved to eth0
first. But then again, opening /dev/sda1 is also a resolution
procedure (finding the kdev_t for sda1), though it is in the kernel.

I am reminded of Solaris, which has device nodes for network
interfaces in /dev, though I am not aware how they are actually used.
(And granted, having to plumb it first is not as straightforward
compared to just-using-them in Linux). Though, when it is a device
node, userspace does not need to have knowledge of /dev/net and
readlink(2) it itself, as the kernel will auto-follow symlinks when
open(2)ed.
--
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