linux-kernel - Re: ipw2200 device naming problems in 2.6.20-rc2-git1

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: <4597A5A9.70301@ens-lyon.org>
Date:	Sun, 31 Dec 2006 12:57:29 +0100
From:	Brice Goglin <Brice.Goglin@...-lyon.org>
To:	Robert Hancock <hancockr@...w.ca>
CC:	linux-kernel <linux-kernel@...r.kernel.org>
Subject: Re: ipw2200 device naming problems in 2.6.20-rc2-git1

Robert Hancock wrote:
> Having some intermittent problems using my ipw2200 wireless card on
> 2.6.20-rc2-git1 (may affect earlier versions as well) under Fedora
> Core 6 i386. It appears that sometimes on bootup the interface gets
> named with a junk name like __tmp32284835 and it doesn't show up in
> ifconfig. rmmod/insmod on ipw2200 fixes the problem and it shows up as
> eth1 again. I don't think this problem happened with Fedora 2.6.18
> kernels..
>

I've seen some problems like this with kernels <= 2.6.19. But it is now
fixed since the following commit (merged in rc1 IIRC). The symptoms were
that it the interface was getting a strange name (something like
"eth0_tmp") when udev was renaming it with DRIVERS=="?*" in the rule.
See http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=389250. I removed
DRIVERS from the rule to avoid the problem, but the following commit was
definitely fixing the problem at this point. I didn't check again recently.

Brice



commit 1901fb2604fbcd53201f38725182ea807581159e
Author: Kay Sievers <kay.sievers@...ell.com>
Date:   Sat Oct 7 21:55:55 2006 +0200

    Driver core: fix "driver" symlink timing

    Create the "driver" link before the child device may be created by
    the probing logic. This makes it possible for userspace (udev), to
    determine the driver property of the parent device, at the time the
    child device is created.

    Signed-off-by: Kay Sievers <kay.sievers@...ell.com>
    Signed-off-by: Greg Kroah-Hartman <gregkh@...e.de>


-
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/