linux-kernel - Re: MUSB crash on OMAP3 board with second load of gadget

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: <48239d391001220238r151c4dfbjd8f6e7863718dad8@mail.gmail.com>
Date:	Fri, 22 Jan 2010 13:38:19 +0300
From:	Sergey Lapin <slapinid@...il.com>
To:	me@...ipebalbi.com
Cc:	felipe.balbi@...ia.com,
	"linux-omap@...r.kernel.org" <linux-omap@...r.kernel.org>,
	"linux-usb@...r.kernel.org" <linux-usb@...r.kernel.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	David Brownell <dbrownell@...rs.sourceforge.net>
Subject: Re: MUSB crash on OMAP3 board with second load of gadget

Hi,

> [  580.082427] [<c0030ac4>] (__irq_svc+0x44/0xa8) from [<c00420dc>]
> (omap3_enter_idle+0x124/0x158)
> [  580.091186] [<c00420dc>] (omap3_enter_idle+0x124/0x158) from
> [<c022d708>] (cpuidle_idle_call+0xa4/0x180)
> [  580.100738] [<c022d708>] (cpuidle_idle_call+0xa4/0x180) from
> [<c00324dc>] (cpu_idle+0x48/0x98)
> [  580.109436] [<c00324dc>] (cpu_idle+0x48/0x98) from [<c0008934>]
> (start_kernel+0x268/0x2c8)
> [  580.117767] [<c0008934>] (start_kernel+0x268/0x2c8) from
> [<80008034>] (0x80008034)
> [  580.125366] Code: c03a876b e92d4013 e5903004 e1a04000 (e593c000)
> [  580.131652] ---[ end trace 42b8f4f7e396999c ]---
> [  580.136291] Kernel panic - not syncing: Fatal exception in interrupt
>

I've managed to debug that in my case,
drivers/usb/musb/musb_gadget_ep0.c:
musb_read_setup():
        /* clean up any leftover transfers */
        r = next_ep0_request(musb);
in this place we have somewhat corrupted usb_request. Any ideas why?

By the way, crash is not reproduced if cable is removed before module unloading
(and all USB activity processed).

S.
--
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/