linux-kernel - Re: PROBLEM: kernel oops with g

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, 24 Jun 2009 01:54:20 -0700
From:	David Brownell <david-b@...bell.net>
To:	Alan Cox <alan@...rguk.ukuu.org.uk>
Cc:	Marek Szyprowski <m.szyprowski@...sung.com>,
	"'Alan Stern'" <stern@...land.harvard.edu>,
	"'Peter Korsgaard'" <jacmet@...site.dk>,
	"'USB list'" <linux-usb@...r.kernel.org>,
	"'Kernel development list'" <linux-kernel@...r.kernel.org>,
	kyungmin.park@...sung.com
Subject: Re: PROBLEM: kernel oops with g_serial USB gadget on 2.6.30

On Wednesday 24 June 2009, Alan Cox wrote:
> Looks to me like the gs_write_room function takes a lock already held
> when the driver calls tty_flip_buffer_push() - which will and can call
> back into the driver (eg for echo processing)

That doesn't seem to explain whatever null pointer was being
traversed though.

A lock-already-held problem would self-deadlock, not oops.

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