All of lore.kernel.org
 help / color / mirror / Atom feed
From: Johan Hedberg <johan.hedberg@gmail.com>
To: Szymon Janc <szymon.janc@tieto.com>
Cc: Gustavo Padovan <gustavo@padovan.org>,
	"linux-bluetooth@vger.kernel.org"
	<linux-bluetooth@vger.kernel.org>
Subject: Re: [PATCH 1/2] Bluetooth: Fix legacy pairing with some devices
Date: Fri, 29 Jun 2012 13:56:53 +0300	[thread overview]
Message-ID: <20120629105653.GA17737@x220> (raw)
In-Reply-To: <201205300941.34495.szymon.janc@tieto.com>

Hi Szymon & Gustavo,

On Wed, May 30, 2012, Szymon Janc wrote:
> > > Some devices e.g. SonyEricsson Xperia ray and arc S don't do SDP search
> > > before pairing. No L2CAP is connected so default HCI_DISCONN_TIMEOUT
> > > (2 seconds) timeout value is being used. This results in problems with
> > > legacy pairing as remote user has only few seconds to enter PIN before
> > > ACL is disconnected.
> > > 
> > > Increase disconnect timeout to HCI_PAIRING_TIMEOUT if SSP is disabled
> > > and no linkey exists.
> > 
> > does this only happen with SSP disabled?
> 
> Yes, I've seen this only with SSP disabled.
> After name request remote devices ask user to enter PIN and before user is
> able to do so (4 sec only) link is disconnected (cause we didn't get pin
> request event yet).
> 
> For SSP hci_conn_hold is called in hci_io_capa_request_evt so link is not
> disconnected.
> 
> > 
> > Also add the hcidump output to the commit message would be helpful.
> 
> hcidump for ssp disabled [1] and ssp enabled [2] below.
> 
> > > 
> > > Signed-off-by: Szymon Janc <szymon.janc@tieto.com>
> > > ---
> > >  net/bluetooth/hci_event.c |    7 ++++++-
> > >  1 file changed, 6 insertions(+), 1 deletion(-)
> > > 
> > > diff --git a/net/bluetooth/hci_event.c b/net/bluetooth/hci_event.c
> > > index ac86b65..98e8020 100644
> > > --- a/net/bluetooth/hci_event.c
> > > +++ b/net/bluetooth/hci_event.c
> > > @@ -1762,7 +1762,12 @@ static void hci_conn_complete_evt(struct hci_dev *hdev, struct sk_buff *skb)
> > >  		if (conn->type == ACL_LINK) {
> > >  			conn->state = BT_CONFIG;
> > >  			hci_conn_hold(conn);
> > > -			conn->disc_timeout = HCI_DISCONN_TIMEOUT;
> > > +
> > > +			if (!hci_conn_ssp_enabled(conn) &&
> > > +			    !hci_find_link_key(hdev, &ev->bdaddr))
> 
> I could add also checking if connection is incoming to narrow case a bit further...
> 
> > > +				conn->disc_timeout = HCI_PAIRING_TIMEOUT;
> > > +			else
> > > +				conn->disc_timeout = HCI_DISCONN_TIMEOUT;
> > 
> > You are also changing the timeout for a SDP search, for example, to
> > HCI_PAIRING_TIMEOUT and this is not good. I think we need to be smarter here,
> > we can't change the behaviour of things like SDP search here.
> 
> Maybe we could set timeout back to HCI_DICONN_TIMEOUT when l2cap is
> connected (or disconnected)?  That should cover SDP search case..

What happened to getting this patch upstream? To me it looks like a
definitely needed fix. After adding the fix to restore a sensible value
for disc_timeout after an L2CAP connect request either way and adding a
better explanation to the commit message (that we only get the PIN
request after user has entered one on the remote side, including a
hcidump of this) I think this should go upstream. If this had been
processed in a timely manner it could have made it to 3.5 but now it
seems too late for that (as it's not strictly speaking a regression from
3.4).

Johan

  reply	other threads:[~2012-06-29 10:56 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-28  9:47 [PATCH 1/2] Bluetooth: Fix legacy pairing with some devices Szymon Janc
2012-05-28  9:47 ` [PATCH 2/2] Bluetooth: Remove unused HCI timeouts definitions Szymon Janc
2012-05-29 17:39   ` Gustavo Padovan
2012-05-29 17:37 ` [PATCH 1/2] Bluetooth: Fix legacy pairing with some devices Gustavo Padovan
2012-05-30  7:41   ` Szymon Janc
2012-06-29 10:56     ` Johan Hedberg [this message]
2012-07-04  7:56       ` Gustavo Padovan
2012-07-19  9:13         ` Szymon Janc
2012-07-19  9:34           ` Johan Hedberg
2012-07-19 10:17             ` Szymon Janc
2012-07-19 10:25               ` Johan Hedberg

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=20120629105653.GA17737@x220 \
    --to=johan.hedberg@gmail.com \
    --cc=gustavo@padovan.org \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=szymon.janc@tieto.com \
    /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.