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
| ||
|
Message-ID: <adaejfhzlnh.fsf@cisco.com> Date: Fri, 26 Oct 2007 13:05:54 -0700 From: Roland Dreier <rdreier@...co.com> To: Adam Baker <linux@...er-net.org.uk> Cc: rt2400-devel@...ts.sourceforge.net, Ivo van Doorn <ivdoorn@...il.com>, linux-kernel@...r.kernel.org, kernel-stuff@...cast.net Subject: Re: [Rt2400-devel] [PATCH] rt2500usb - Don't claim 050d:705{0/a} > The function that is returning ENODEV is the driver probe function. According > to Documentation/DocBook/writing_usb_driver/ch03.html when that function is > called > > "The driver now needs to verify that this device is actually one that it can > accept. If so, it returns 0. If not, or if any error occurs during > initialization, an errorcode (such as -ENOMEM or -ENODEV) is returned from > the probe function." > > It isn't a device the driver can accept so it returns -ENODEV That's all true but irrelevant. That error return isn't propagated back to userspace when it runs modprobe (and in fact it *can't* be sanely returned to userspace -- what do you do if the probe function succeeds for two devices and fails for a third?). So there's not really any way for userspace to loop through a list of modules until one succeeds. - 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/
Powered by blists - more mailing lists