From: David Brownell <david-b@pacbell.net>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Marek Szyprowski <m.szyprowski@samsung.com>,
"'Alan Stern'" <stern@rowland.harvard.edu>,
"'Peter Korsgaard'" <jacmet@sunsite.dk>,
"'USB list'" <linux-usb@vger.kernel.org>,
"'Kernel development list'" <linux-kernel@vger.kernel.org>,
kyungmin.park@samsung.com
Subject: Re: PROBLEM: kernel oops with g_serial USB gadget on 2.6.30
Date: Wed, 24 Jun 2009 01:54:20 -0700 [thread overview]
Message-ID: <200906240154.21349.david-b@pacbell.net> (raw)
In-Reply-To: <20090624094240.4097db11@lxorguk.ukuu.org.uk>
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.
next prev parent reply other threads:[~2009-06-24 8:54 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-22 12:04 PROBLEM: kernel oops with g_serial USB gadget on 2.6.30 Marek Szyprowski
2009-06-22 12:33 ` Peter Korsgaard
2009-06-22 13:55 ` Marek Szyprowski
2009-06-22 14:06 ` Peter Korsgaard
2009-06-22 14:06 ` Alan Stern
2009-06-22 14:12 ` Marek Szyprowski
2009-06-22 15:02 ` Alan Stern
2009-06-23 3:26 ` David Brownell
2009-06-23 6:41 ` Marek Szyprowski
2009-06-23 7:22 ` David Brownell
2009-06-23 8:37 ` Marek Szyprowski
2009-06-23 9:21 ` Alan Cox
2009-06-23 9:33 ` Marek Szyprowski
2009-06-23 9:54 ` Alan Cox
2009-06-23 15:00 ` Marek Szyprowski
2009-06-23 16:47 ` David Brownell
2009-06-23 16:52 ` David Brownell
2009-06-24 7:07 ` Marek Szyprowski
2009-06-24 8:42 ` Alan Cox
2009-06-24 8:54 ` David Brownell [this message]
2009-06-24 8:49 ` David Brownell
2009-06-24 10:30 ` Marek Szyprowski
2009-06-24 23:43 ` David Brownell
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200906240154.21349.david-b@pacbell.net \
--to=david-b@pacbell.net \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=jacmet@sunsite.dk \
--cc=kyungmin.park@samsung.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=m.szyprowski@samsung.com \
--cc=stern@rowland.harvard.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox