linux-kernel - Re: [PATCH] [usb-serial] fix Ooops on uplug

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:	Tue, 21 Jul 2009 17:56:20 +0200
From:	Daniel Mack <daniel@...aq.de>
To:	Alan Stern <stern@...land.harvard.edu>
Cc:	Alan Cox <alan@...rguk.ukuu.org.uk>,
	Kernel development list <linux-kernel@...r.kernel.org>,
	USB list <linux-usb@...r.kernel.org>
Subject: Re: [PATCH] [usb-serial] fix Ooops on uplug

On Tue, Jul 21, 2009 at 11:53:35AM -0400, Alan Stern wrote:
> [  961.903814]  [<c1021755>] warn_slowpath_null+0xd/0x10
> [  961.903907]  [<c103ed98>] __lock_acquire+0x395/0xaf5
> [  961.903999]  [<c103ddb9>] ? mark_lock+0x1e/0x1e4
> [  961.904020]  [<c103f540>] lock_acquire+0x48/0x64
> [  961.904020]  [<c1126810>] ? tty_port_close_start+0x1a/0x118
> [  961.904020]  [<c11c21ef>] _spin_lock_irqsave+0x2e/0x3e
> [  961.904020]  [<c1126810>] ? tty_port_close_start+0x1a/0x118
> [  961.904020]  [<c1126810>] tty_port_close_start+0x1a/0x118
> [  961.904020]  [<f09649b5>] serial_close+0x4f/0x7b [usbserial]
> [  961.904020]  [<c11215e3>] tty_release_dev+0x17c/0x400
> [  961.904020]  [<c103d28e>] ? register_lock_class+0x17/0x272
> [  961.904020]  [<c1121879>] tty_release+0x12/0x1c
> [  961.904020]  [<c107201f>] __fput+0xe9/0x172
> [  961.904020]  [<c10720c1>] fput+0x19/0x1c
> [  961.904020]  [<c106f93c>] filp_close+0x51/0x5b
> [  961.904020]  [<c106f9b0>] sys_close+0x6a/0xa4
> [  961.904020]  [<c1002a08>] sysenter_do_call+0x12/0x36
> [  961.904020] ---[ end trace ed6ce19124f40616 ]---
> 
> This is only a lockdep warning, and I don't understand its
> significance.  Even worse, when I plugged in a USB flash drive
> afterward this appeared:

The problem is that freed resources are accessed, and that can lead to
any kind of strange kernel faults from crashing to other subsequent
errors.

Did you try my patch?

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