linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: Mat Martineau <mathewm@codeaurora.org>
Cc: Andrei Emeltchenko <Andrei.Emeltchenko.news@gmail.com>,
	linux-bluetooth@vger.kernel.org, gustavo@padovan.org
Subject: Re: [PATCH 1/6] Bluetooth: Fix deadlock when closing socket
Date: Thu, 06 Sep 2012 13:10:51 -0700	[thread overview]
Message-ID: <1346962251.21200.119.camel@aeonflux> (raw)
In-Reply-To: <alpine.DEB.2.02.1209060946190.22884@mathewm-linux>

Hi Mat,

> > If we have unacked frames when closing bluetooth socket we deadlock
> > since conn->chan_lock, chan->lock and socket lock are taken. Remove
> > __l2cap_wait_ack completely.
> >
> > Signed-off-by: Andrei Emeltchenko <andrei.emeltchenko@intel.com>
> 
> I don't think you want to remove this code completely, at least not 
> without giving some thought to the problem it is solving.
> 
> The problem is that programs may have an open socket which they send 
> some data on, then immediately close.  There is no feedback when data 
> is actually sent over the air, so the socket may end up getting torn 
> down while there is still data in the HCI tx buffer or some data was 
> lost and needs to be retransmitted.  Waiting for an acknowledgement 
> confirms that the application's sent data made it to the remote 
> device.
> 
> Without this code, it's difficult to use l2test on a number of 
> qualification tests.  Profiles or applications using ERTM may depend 
> on the "wait for ack before closing" behavior in order to have a clean 
> disconnect.

isn't that what we have SO_LINGER for?

Regards

Marcel



  reply	other threads:[~2012-09-06 20:10 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-06 12:05 [PATCH 1/6] Bluetooth: Fix deadlock when closing socket Andrei Emeltchenko
2012-09-06 12:05 ` [PATCH 2/6] Bluetooth: Fix freeing uninitialized delayed works Andrei Emeltchenko
2012-09-06 17:03   ` Mat Martineau
2012-09-08 20:28   ` Gustavo Padovan
2012-09-06 12:05 ` [PATCH 3/6] Bluetooth: trivial: Make hci_chan_del return void Andrei Emeltchenko
2012-09-08 20:33   ` Gustavo Padovan
2012-09-06 12:05 ` [PATCH 4/6] Bluetooth: trivial: Remove empty line Andrei Emeltchenko
2012-09-08 20:34   ` Gustavo Padovan
2012-09-06 12:05 ` [PATCH 5/6] Bluetooth: debug: Print refcnt for hci_dev Andrei Emeltchenko
2012-09-08 21:13   ` Gustavo Padovan
2012-09-06 12:05 ` [PATCH 6/6] Bluetooth: AMP: Add Read Data Block Size to amp_init Andrei Emeltchenko
2012-09-08 21:14   ` Gustavo Padovan
2012-09-06 17:01 ` [PATCH 1/6] Bluetooth: Fix deadlock when closing socket Mat Martineau
2012-09-06 20:10   ` Marcel Holtmann [this message]
2012-09-07 14:08     ` Andrei Emeltchenko
2012-09-07 17:00       ` Mat Martineau
2012-09-08 21:05         ` Gustavo Padovan
2012-09-10  8:23         ` [RFCv0] Bluetooth: Fix SO_LINGER in L2CAP Andrei Emeltchenko
2012-09-10 10:43           ` Anderson Lizardo
2012-09-10 10:55             ` Andrei Emeltchenko
2012-09-07 14:07   ` [PATCH 1/6] Bluetooth: Fix deadlock when closing socket Andrei Emeltchenko

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=1346962251.21200.119.camel@aeonflux \
    --to=marcel@holtmann.org \
    --cc=Andrei.Emeltchenko.news@gmail.com \
    --cc=gustavo@padovan.org \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=mathewm@codeaurora.org \
    /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;
as well as URLs for NNTP newsgroup(s).