netdev - Re: problem with kernel ipconfig over usb ethernet on v.2.6.33-rc3

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]

Date:	Sun, 10 Jan 2010 13:38:48 -0800 (PST)
From:	David Miller <davem@...emloft.net>
To:	chripell@...il.com
Cc:	netdev@...r.kernel.org
Subject: Re: problem with kernel ipconfig over usb ethernet on v.2.6.33-rc3

From: christian pellegrin <chripell@...il.com>
Date: Sun, 10 Jan 2010 09:27:48 +0100

> Hi,
> 
> I noticed that kernel IP auto-configuration is not usable for
> USB-ethenet dongles on newer kernel because it starts before the USB
> devices are found (perhaps as a consequence of parallelization of
> kernel boot; the built-in delay of 500ms is not enough).I'm using the
> following patch (with a command line parameter ipconfigdelay=10) to
> solve this situation, but it's a shameless cut & paste from rootdelay.
> Is there any better solution or I'm just missing something?

How long does it actually take for the USB ethernet device
to become visible at this point?

Is 2 seconds enough?  For example.

If so, let's just change CONF_PRE_OPEN to "2" and change
msleep() to ssleep().

It's rediculious to require that users learn about obscure
kernel command line options in order for basic functionality
to work properly.
--
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