| 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: Wed, 08 Apr 2009 12:32:14 -0500 From: Larry Finger <Larry.Finger@...inger.net> To: alan-jenkins@...fmail.co.uk CC: Rusty Russell <rusty@...tcorp.com.au>, Arjan van de Ven <arjan@...ux.intel.com>, LKML <linux-kernel@...r.kernel.org>, "Rafael J. Wysocki" <rjw@...k.pl>, wireless <linux-wireless@...r.kernel.org> Subject: Re: Regression in 2.6.30-rc1 since commit acae0515 - wireless broken Alan Jenkins wrote: > On 4/8/09, Larry Finger <Larry.Finger@...inger.net> wrote: > > Something is very wrong with request_module(), this is just the most > obvious symptom. It also seems to affect libusual (loading > usb-storage) and FAT (loading NLS modules). > > If I hotplug my wireless device, it then loads correctly. So I'm > guessing wireless modules e.g. encryption modules get loaded too > asynchronously. I.e. on boot, the sub-modules are loaded too late. > But when I hotplug the device, the modules are already loaded. > > Same with FAT - it fails on first attempt to mount because of missing > NLS module, then works on second mount, > > I agree that commit looks like it should be a no-op though :-). > I will try to confirm the OP's bisection by reverting the commit, acae0515. I added printk's to the entry and exit from __request_module and obtained the following: module: __request_module entered for module snd-hda-codec-id:14f15051 module: loading module snd-hda-codec-id:14f15051 - call_usermodehelper returned 0 module: __request_module entered for module ecb(arc4) module: loading module ecb(arc4) - call_usermodehelper returned 256 module: __request_module entered for module ecb module: loading module ecb - call_usermodehelper returned 0 module: __request_module entered for module char-major-4-68 module: loading module char-major-4-68 - call_usermodehelper returned 256 module: __request_module entered for module char-major-4 module: loading module char-major-4 - call_usermodehelper returned 256 module: __request_module entered for module char-major-4-69 module: loading module char-major-4-69 - call_usermodehelper returned 256 module: __request_module entered for module char-major-4 module: loading module char-major-4 - call_usermodehelper returned 256 module: __request_module entered for module char-major-4-70 module: loading module char-major-4-70 - call_usermodehelper returned 256 module: __request_module entered for module char-major-4 module: loading module char-major-4 - call_usermodehelper returned 256 module: __request_module entered for module char-major-4-71 module: loading module char-major-4-71 - call_usermodehelper returned 256 module: __request_module entered for module char-major-4 module: loading module char-major-4 - call_usermodehelper returned 256 module: __request_module entered for module net-pf-10 module: loading module net-pf-10 - call_usermodehelper returned 256 module: __request_module entered for module net-pf-10 module: loading module net-pf-10 - call_usermodehelper returned 256 module: __request_module entered for module net-pf-10 module: loading module net-pf-10 - call_usermodehelper returned 256 module: __request_module entered for module net-pf-10 module: loading module net-pf-10 - call_usermodehelper returned 256 module: __request_module entered for module net-pf-10 module: loading module net-pf-10 - call_usermodehelper returned 256 module: __request_module entered for module net-pf-10 module: loading module net-pf-10 - call_usermodehelper returned 256 module: __request_module entered for module net-pf-10 module: loading module net-pf-10 - call_usermodehelper returned 256 module: __request_module entered for module net-pf-10 module: loading module net-pf-10 - call_usermodehelper returned 256 module: __request_module entered for module net-pf-10 module: loading module net-pf-10 - call_usermodehelper returned 256 module: __request_module entered for module net-pf-10 module: loading module net-pf-10 - call_usermodehelper returned 256 module: __request_module entered for module net-pf-10 module: loading module net-pf-10 - call_usermodehelper returned 256 module: __request_module entered for module net-pf-10 module: loading module net-pf-10 - call_usermodehelper returned 256 module: __request_module entered for module net-pf-10 module: loading module net-pf-10 - call_usermodehelper returned 256 module: __request_module entered for module net-pf-10 module: __request_module entered for module net-pf-10 module: loading module net-pf-10 - call_usermodehelper returned 256 module: loading module net-pf-10 - call_usermodehelper returned 256 module: __request_module entered for module net-pf-10 module: loading module net-pf-10 - call_usermodehelper returned 256 module: __request_module entered for module net-pf-10 module: loading module net-pf-10 - call_usermodehelper returned 256 module: __request_module entered for module net-pf-10 module: loading module net-pf-10 - call_usermodehelper returned 256 module: __request_module entered for module net-pf-10 module: loading module net-pf-10 - call_usermodehelper returned 256 module: __request_module entered for module net-pf-10 module: loading module net-pf-10 - call_usermodehelper returned 256 module: __request_module entered for module net-pf-10 module: loading module net-pf-10 - call_usermodehelper returned 256 According to the description of the routine, it should return 0 on success and a negative number for an error. Where do the values of "256" mean? Larry -- 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