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: <81b0412b0908021125x654fd337hf03a67385302d6e4@mail.gmail.com>
Date:	Sun, 2 Aug 2009 20:25:00 +0200
From:	Alex Riesen <raa.lkml@...il.com>
To:	Oliver Neukum <oliver@...kum.org>
Cc:	linux-usb@...r.kernel.org, Oliver Neukum <oliver@...kum.name>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Greg Kroah-Hartman <greg@...ah.com>,
	Alan Cox <alan@...rguk.ukuu.org.uk>
Subject: Re: Oops in CDC ACM after an Openmoko phone (neo1973) changes its usb 
	interface from ACM to Ethernet

On Sun, Aug 2, 2009 at 19:19, Oliver Neukum<oliver@...kum.org> wrote:
> Am Sonntag, 2. August 2009 18:40:56 schrieb Alex Riesen:
>> [   75.453444] Call Trace:
>> [   75.453444]  [<ffffffff812a77b2>] usb_autopm_get_interface+0xe/0x10
>> [   75.453444]  [<ffffffffa0072e19>] acm_port_down+0x3f/0x1bb [cdc_acm]
>> [   75.453444]  [<ffffffff811f0af1>] ? tty_port_close_start+0xc1/0x153
>> [   75.453444]  [<ffffffffa0073258>] acm_tty_close+0x3d/0x83 [cdc_acm]
>> [   75.453444]  [<ffffffff811eaca7>] tty_release_dev+0x1bf/0x4e8
>> [   75.453444]  [<ffffffffa00732c3>] ? acm_tty_open+0x25/0x2ae [cdc_acm]
>
> This can happen only if acm_port_down() fails to detect that the device has
> been disconnected, as it calls usb_autopm_get_interface()
> only if acm->dev != NULL.
> This however should not happen if acm_disconnect runs.
>
> Can you put a printk into acm_disconnect and recompile with CONFIG_USB_DEBUG?

I put the printks at some random lines in acm_disconnect (as of v2.6.31-rc2)
and turned CONFIG_USB_DEBUG on. It is definitely not the same kernel
I tried before (and sadly, it does not go oops), but it still has
tty_port_close_start: count = -1
Dmesg attached

I'm retrying with recent kernels (hopefully I'll get enough data left
on the screen),
I shall try to find the -rc2 which oopses (I suspect it is the one
just before -rc3).

Download attachment "usbdeb" of type "application/octet-stream" (73122 bytes)

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ