linux-kernel - Re: 2.6.18-rc4-mm[1,2,3] -- Network card not getting assigned an "eth" device name

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: <20060828.132717.57158097.davem@davemloft.net>
Date:	Mon, 28 Aug 2006 13:27:17 -0700 (PDT)
From:	David Miller <davem@...emloft.net>
To:	akpm@...l.org
Cc:	miles.lane@...il.com, dcbw@...hat.com,
	linux-kernel@...r.kernel.org, netdev@...r.kernel.org,
	jeremy@...p.org, rml@...ell.com
Subject: Re: 2.6.18-rc4-mm[1,2,3] -- Network card not getting assigned an
 "eth" device name

From: Andrew Morton <akpm@...l.org>
Date: Mon, 28 Aug 2006 12:03:28 -0700

> grepping for `ioctl' gives:
> 
> ioctl(9, SIOCGIWNAME, 0xbfe38d8c)                 = -1 EINVAL (Invalid argument)
> ioctl(9, SIOCETHTOOL, 0xbfe38d2c)                 = 0
> ioctl(11, SIOCGIFHWADDR, {ifr_name="eth0", ???})  = -1 ENODEV (No such device)
> ioctl(11, SIOCGIFFLAGS, {ifr_name="eth0", ???})   = -1 ENODEV (No such device)
> 
> Perhaps you could generate the strace output for 2.6.18-rc5, grep that for
> ioctl, look for differences?  That initial SIOCGIWNAME failure is fishy.

That might help, but SIOCGIWNAME just gets a string that
says what wireless mode the device is in, not the device
name.  Althought NetworkManager might use this for something
interesting.

All of the interesting config calls are probably happening
via netlink, which doesn't get decoded by strace.

But changes via netlink can get traced by using "ip" in monitor mode,
try "ip monitor all" as root during such a NetworkManager run.
-
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/