From: Marcel Holtmann <marcel@holtmann.org>
To: Mat Martineau <mathewm@codeaurora.org>
Cc: linux-bluetooth@vger.kernel.org, gustavo@padovan.org,
pkrystad@codeaurora.org
Subject: Re: [PATCHv2] Bluetooth: Send a configuration request after security confirmation
Date: Wed, 23 May 2012 05:12:18 +0200 [thread overview]
Message-ID: <1337742738.15105.30.camel@aeonflux> (raw)
In-Reply-To: <1337720145-8019-1-git-send-email-mathewm@codeaurora.org>
Hi Mat,
> Sometimes an ACL link must be raised to a higher security level after
> an L2CAP connection is requested, but before a connection response is
> sent. In this case, a connection response sent by L2CAP was not
> immediately followed by a configuration request. Other code paths do
> send this configuration request right away. It was possible for the
> connection to time out while L2CAP waited for the remote device (like
> PTS) to trigger the configuration process.
>
> This change immediately sends a configuration request after a connect
> response rather than waiting for a configuration request from the
> remote device. It fixes connection stalls in a variety of PTS test
> cases.
any change you can add a before and after hcidump in the commit message?
Regards
Marcel
next prev parent reply other threads:[~2012-05-23 3:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-22 20:55 [PATCHv2] Bluetooth: Send a configuration request after security confirmation Mat Martineau
2012-05-23 3:12 ` Marcel Holtmann [this message]
2012-05-23 21:59 ` [PATCHv3] " Mat Martineau
2012-05-24 0:28 ` Marcel Holtmann
2012-05-24 0:33 ` Gustavo Padovan
2012-05-23 8:20 ` [PATCHv2] " 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=1337742738.15105.30.camel@aeonflux \
--to=marcel@holtmann.org \
--cc=gustavo@padovan.org \
--cc=linux-bluetooth@vger.kernel.org \
--cc=mathewm@codeaurora.org \
--cc=pkrystad@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