| 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
| ||
|
Date: Fri, 17 Apr 2009 01:23:16 -0700 (PDT) From: David Miller <davem@...emloft.net> To: dmitry.krivoschekov@...il.com Cc: netdev@...r.kernel.org Subject: Re: [PATCH 0/3] From: dmitry.krivoschekov@...il.com Date: Thu, 16 Apr 2009 13:37:36 +0400 > this patch series adds some flexibility to ip_auto_config() function. > Currently the function assumes that 500 msec delay before opening > a network device is enough, but it's not true for some h/w configurations, > e.g. if you're using a USB network device. > In my case it may take up to 2 seconds before the device gets available > for opening. I think this problem space would be served better by a scheme that just worked automatically. If the user put nfsroot= onto the kernel command line, the expectation is that the device is expected to be there. Therefore it is reasonable to make the ipconfig.c code do a loop periodically retrying to open the intended network device. And after several seconds of iterations, fail. Heck, it doesn't even need to do anything fancy. After the initial attempt, it can simply wait for the NETDEV_REGISTER notifier event. Then it will know exactly when the device shows up. In fact you won't need anything to implement this, simply register the notifier and make the notifier trigger the ipconfig.c code to do a DHCP or RARP probe or whatever when the device we're interested in appears. I'm not applying these patches, sorry. -- 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
Powered by blists - more mailing lists