Re: [PATCHv2 2/2] Bluetooth: Lock the L2CAP channel when sending

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi Gustavo,

On Fri, May 04, 2012 at 09:01:04PM -0300, Gustavo Padovan wrote:
> Hi Mat,
> 
> * Mat Martineau <mathewm@xxxxxxxxxxxxxx> [2012-05-04 14:20:31 -0700]:
> 
> > The ERTM and streaming mode transmit queue must only be accessed while
> > the L2CAP channel lock is held.  Locking the channel before calling
> > l2cap_chan_send ensures that multiple threads cannot simultaneously
> > manipulate the queue when sending and receiving concurrently.
> > 
> > L2CAP channel locking had previously moved to the l2cap_chan struct
> > instead of the associated socket, so some of the old socket locking
> > can also be removed in this patch.
> > 
> > Signed-off-by: Mat Martineau <mathewm@xxxxxxxxxxxxxx>
> > ---
> >  include/net/bluetooth/bluetooth.h |    2 --
> >  net/bluetooth/l2cap_sock.c        |   19 +++++++++++--------
> >  2 files changed, 11 insertions(+), 10 deletions(-)
> 
> Patch has been applied to the bluetooth tree. Thanks.

What about applying the first patch? I actually pulled that patch from
bluetooth-next and modified locking in my code but now that patch seems to
be lost.

Best regards 
Andrei Emeltchenko 

--
To unsubscribe from this list: send the line "unsubscribe linux-bluetooth" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[Index of Archives]     [Bluez Devel]     [Linux Wireless Networking]     [Linux Wireless Personal Area Networking]     [Linux ATH6KL]     [Linux USB Devel]     [Linux Media Drivers]     [Linux Audio Users]     [Linux Kernel]     [Linux SCSI]     [Big List of Linux Books]

  Powered by Linux