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:	Wed, 08 Apr 2009 23:46:37 -0700
From:	Justin Madru <jdm64@...ab.com>
To:	Kay Sievers <kay.sievers@...y.org>
CC:	Andrew Morton <akpm@...ux-foundation.org>,
	lkml <linux-kernel@...r.kernel.org>, linux-scsi@...r.kernel.org,
	linux-usb@...r.kernel.org, Arjan van de Ven <arjan@...radead.org>
Subject: Re: 2.6.30-rc1: OOPS on usb disk insert

Kay Sievers wrote:
> On Tue, Apr 7, 2009 at 23:07, Justin Madru <jdm64@...ab.com> wrote:
>   
>> Andrew Morton wrote:
>>     
>>> On Tue, 07 Apr 2009 22:05:24 -0700 Justin Madru <jdm64@...ab.com> wrote:
>>>       
>
>   
>>>> Testing out .30-rc1 and usb devises don't work. I insert my flash disk
>>>> and get this oops.
>>>>         
>
>   
>>> The trace appears to be claiming that kernel/async.c:async_new.func is
>>> NULL.
>>>
>>> But it cannot be - it's initialised at compilation time.  Unless
>>> something scribbled on it of course.
>>>       
>
> I've seen async problems with other subsystem too, maybe caused by a
> corruption which is fixed by:
>   http://patchwork.kernel.org/patch/16776/
>
>   -static void __init acpi_battery_init_async(void *unused, ...
>   +static void acpi_battery_init_async(void *unused, ...
>
> Kay
>
>   
I've applied the following patches (to try to fix other bugs) and I no 
longer get a BUG/OOPS
although the patches might have not been the cause of the fix, but 
inserting the disk still doesn't works.

http://patchwork.kernel.org/patch/17199/
http://patchwork.kernel.org/patch/17025/
http://patchwork.kernel.org/patch/17039/

It now complains of: FAT: IO charset cp437 not found
Which I've found a work around by:

<insert flash disk>
syslog complains: FAT: IO charset cp437 not found
sudo modprobe -r nls_cp437
sudo modprobe -i nls_cp437
<remove then reinsert flash disk>
syslog complains: FAT: IO charset iso8859_1 not found
sudo modprobe -r nls_iso8859_1
sudo modprobe -i nls_iso8859_1
<insert flash disk>
profit!!

So, I have to insert the disk 3 times before it works. although after 
that it just works, until I reboot and I have to repeat the unload/load 
modules.

Justin Madru

--
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

Powered by Openwall GNU/*/Linux Powered by OpenVZ