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]
Message-ID: <4988B494.1020503@ventoso.org>
Date:	Tue, 03 Feb 2009 22:18:12 +0100
From:	Luca Olivetti <luca@...toso.org>
To:	Ingo Molnar <mingo@...e.hu>
CC:	Daniel Walker <dwalker@...o99.com>, Greg KH <gregkh@...e.de>,
	Mauro Carvalho Chehab <mchehab@...radead.org>,
	linux-kernel@...r.kernel.org, Hans Verkuil <hverkuil@...all.nl>,
	Janne Grunau <janne-dvb@...nau.be>
Subject: Re: [crash] af9005_usb_module_init(): BUG: unable to handle kernel
 paging request at ff100000

En/na Luca Olivetti ha escrit:
> En/na Ingo Molnar ha escrit:
>> * Daniel Walker <dwalker@...o99.com> wrote:
>>
>>> On Tue, 2009-02-03 at 18:28 +0100, Ingo Molnar wrote:
>>>> FYI, -tip qa keeps triggering this bootup crash occasionally, ever 
>>>> since June 2008 when a DVB merge brought in this new driver:
>>> It looks like it could be a config problem.. The crash happens around 
>>> these two symbol "af9005_rc_keys", and "af9005_rc_keys_size" , and 
>>> they are both defined inside af9005-remote.c different from where the 
>>> init functions is lcoated .. af9005-remote.c needs a special config 
>>> CONFIG_DVB_USB_AF9005_REMOTE to get compiled which you have disabled..
>>
>> ok - but it shouldnt crash, obviously.
> 
> Did you try my suggestion I sent the past December 26th?

The attached patch should be better (sorry it's bzipped, but thunderbird 
crashed three times when I tried to attach it raw), since it initializes 
the remote before calling usb_register.
Could you give it a try?

What I don't know is, if usb_register fails (so making module_init
fail), will module_exit be called nevertheless?
If not, those symbols would be kept and should be freed in module_init
in case usb_register fails.

Bye
-- 
Luca



Download attachment "no_remote_crash.patch.bz2" of type "application/x-bzip" (454 bytes)

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ