From: Andrew Morton <akpm@linux-foundation.org>
To: netdev@vger.kernel.org
Cc: bugme-daemon@bugzilla.kernel.org,
Christopher Head <chead@telus.net>, Daniel Drake <dsd@gentoo.org>,
Alan Cox <alan@lxorguk.ukuu.org.uk>
Subject: Re: [Bugme-new] [Bug 12339] New: ne2000 doesn't set udev DRIVER attribute
Date: Mon, 5 Jan 2009 14:54:27 -0800 [thread overview]
Message-ID: <20090105145427.7d34fc2e.akpm@linux-foundation.org> (raw)
In-Reply-To: <bug-12339-10286@http.bugzilla.kernel.org/>
(switched to email. Please respond via emailed reply-to-all, not via the
bugzilla web interface).
On Wed, 31 Dec 2008 16:44:31 -0800 (PST)
bugme-daemon@bugzilla.kernel.org wrote:
> http://bugzilla.kernel.org/show_bug.cgi?id=12339
>
> Summary: ne2000 doesn't set udev DRIVER attribute
> Product: Networking
> Version: 2.5
> KernelVersion: 2.6.28
> Platform: All
> OS/Version: Linux
> Tree: Mainline
> Status: NEW
> Severity: normal
> Priority: P1
> Component: Other
> AssignedTo: acme@ghostprotocols.net
> ReportedBy: chead@telus.net
>
>
> The ne2000 driver does not set the DRIVER attribute in udev. This causes
> persistent network device naming to ignore the device, thinking it to be a
> virtual device of some sort that ought not to be persistently named.
>
> Relevant output:
> # udevadm info -a -p /sys/class/net/eth0
>
> Udevinfo starts with the device specified by the devpath and then
> walks up the chain of parent devices. It prints for every device
> found, all possible attributes in the udev rules key format.
> A rule to match, can be composed by the attributes of the device
> and the attributes from one single parent device.
>
> looking at device '/devices/virtual/net/eth0':
> KERNEL=="eth0"
> SUBSYSTEM=="net"
> DRIVER==""
> ATTR{addr_len}=="6"
> ATTR{iflink}=="2"
> ATTR{ifindex}=="2"
> ATTR{features}=="0x0"
> ATTR{type}=="1"
> ATTR{link_mode}=="0"
> ATTR{address}=="00:80:c8:2c:71:a2"
> ATTR{broadcast}=="ff:ff:ff:ff:ff:ff"
> ATTR{carrier}=="1"
> ATTR{dormant}=="0"
> ATTR{operstate}=="unknown"
> ATTR{mtu}=="1500"
> ATTR{flags}=="0x1003"
> ATTR{tx_queue_len}=="1000"
>
> looking at parent device '/devices/virtual/net':
> KERNELS=="net"
> SUBSYSTEMS==""
> DRIVERS==""
>
> looking at parent device '/devices/virtual':
> KERNELS=="virtual"
> SUBSYSTEMS==""
> DRIVERS==""
>
>
> Downstream <http://bugs.gentoo.org/show_bug.cgi?id=252449>, Daniel Drake
> suggests that maybe "this is because the driver does not call
> SET_NETDEV_DEV()".
>
parent reply other threads:[~2009-01-05 22:55 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <bug-12339-10286@http.bugzilla.kernel.org/>]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20090105145427.7d34fc2e.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=bugme-daemon@bugzilla.kernel.org \
--cc=chead@telus.net \
--cc=dsd@gentoo.org \
--cc=netdev@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).