From: Russell King <rmk@arm.linux.org.uk>
To: bluez-devel@lists.sourceforge.net
Subject: [Bluez-devel] Re: bug in hci_uart_tx_wakeup() causes panic when UART removed
Date: Sun, 26 Feb 2006 22:47:38 +0000 [thread overview]
Message-ID: <20060226224738.GF31256@flint.arm.linux.org.uk> (raw)
In-Reply-To: <20060226145934.GA18327@hell.org.pl>
On Sun, Feb 26, 2006 at 03:59:35PM +0100, Karol Kozimor wrote:
> Hi,
> Under specific circumstances, hci_uart_tx_wakeup() seems to call
> tty->driver->write() without checking if the tty is alive, which
> effectively causes a nasty panic in uart_write(). From what I've read so
> far it seems that hci_ldisc.c is to blame, so I'm reporting it here.
>
> This is related to:
> http://sourceforge.net/mailarchive/message.php?msg_id=14724441
>
> See also:
> http://bugme.osdl.org/show_bug.cgi?id=6131
> http://bugzilla.kernel.org/show_bug.cgi?id=5958
As a priority, I especially recommend bluetooth developers read:
http://bugzilla.kernel.org/show_bug.cgi?id=5958#c2
where bug 6131 was predicted.
--
Russell King
-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2006-02-26 22:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-26 14:59 [Bluez-devel] bug in hci_uart_tx_wakeup() causes panic when UART removed Karol Kozimor
2006-02-26 21:40 ` Marcel Holtmann
2006-02-26 22:47 ` Russell King [this message]
2006-02-26 23:58 ` [Bluez-devel] " Marcel Holtmann
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=20060226224738.GF31256@flint.arm.linux.org.uk \
--to=rmk@arm.linux.org.uk \
--cc=bluez-devel@lists.sourceforge.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.