[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20140327020909.GA11651@saruman.home>
Date: Wed, 26 Mar 2014 21:09:09 -0500
From: Felipe Balbi <balbi@...com>
To: Peter Hurley <peter@...leysoftware.com>
CC: Felipe Balbi <balbi@...com>, Greg KH <gregkh@...uxfoundation.org>,
Marcel Holtmann <marcel@...tmann.org>,
<linux-serial@...r.kernel.org>, <linux-bluetooth@...r.kernel.org>,
<m-karicheri2@...com>, <b32955@...escale.com>,
Linux OMAP Mailing List <linux-omap@...r.kernel.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 09/11] bluetooth: hci_ldisc: fix deadlock condition
Hi,
On Wed, Mar 26, 2014 at 08:47:15PM -0400, Peter Hurley wrote:
> [ +to Marcel Holtmann ]
>
> On 03/20/2014 03:30 PM, Felipe Balbi wrote:
> >LDISCs shouldn't call tty->ops->write() from within
> >->write_wakeup().
> >
> >->write_wakeup() is called with port lock taken and
> >IRQs disabled, tty->ops->write() will try to acquire
> >the same port lock and we will deadlock.
> >
> >Reviewed-by: Peter Hurley <peter@...leysoftware.com>
> >Reported-by: Huang Shijie <b32955@...escale.com>
> >Signed-off-by: Felipe Balbi <balbi@...com>
>
> I just noticed this patch wasn't addressed to Marcel;
> seems like this should go through the bluetooth tree (but not
> through bluetooth-next because it fixes an oops).
read the archives:
http://marc.info/?l=linux-bluetooth&m=139534449409583&w=2
> Marcel,
>
> You may want to build on top of this patch split handling;
> I noticed some of the protocol drivers are calling
> hci_uart_tx_wakeup() from work functions already (so don't
> need to schedule another work...)
I don't think that should be part of $subject, though.
--
balbi
Download attachment "signature.asc" of type "application/pgp-signature" (820 bytes)
Powered by blists - more mailing lists