From: Johan Hedberg <johan.hedberg@gmail.com>
To: Jaganath Kanakkassery <jaganath.k@samsung.com>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH v5] Bluetooth: Override status if local user rejects pairing
Date: Tue, 24 Jul 2012 15:35:20 +0200 [thread overview]
Message-ID: <20120724133520.GA19450@x220.ice.intel.com> (raw)
In-Reply-To: <1342449675-2842-1-git-send-email-jaganath.k@samsung.com>
Hi Jaganath,
On Mon, Jul 16, 2012, Jaganath Kanakkassery wrote:
> In case if pairing is failed, user cannot differentiate from the status
> whether failure is caused by local rejection or remote rejection
> because authentication failure is coming in both the cases.
>
> This patch overrides the status from controller with "Cancelled"
> in case of local rejection.
>
> This patch will be useful if user can take some action based on local
> or remote rejection
>
> Signed-off-by: Jaganath Kanakkassery <jaganath.k@samsung.com>
> ---
> v5 -> Used STATUS_CANCELLED instead of STATUS_REJECTED
> Added a new flag in hci conn for auth cancel instead of
> a new member in struct
>
> include/net/bluetooth/hci_core.h | 3 ++-
> net/bluetooth/hci_event.c | 19 +++++++++++++++----
> net/bluetooth/mgmt.c | 18 ++++++++++++++++--
> net/bluetooth/smp.c | 3 ++-
> 4 files changed, 35 insertions(+), 8 deletions(-)
Technically the patch looks quite good now. Thanks for implementing the
fix proposals. I had a chat with Marcel and we'd like to have a more
detailed explanation of the exact use case where you need this (i.e.
describe what your agents, etc. are doing and why they can't do what you
want with the current behavior). Also a hcidump showing the local and
remote rejection error codes would be good.
Johan
next prev parent reply other threads:[~2012-07-24 13:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-16 14:41 [PATCH v5] Bluetooth: Override status if local user rejects pairing Jaganath Kanakkassery
2012-07-24 13:35 ` Johan Hedberg [this message]
2012-07-25 9:49 ` Jaganath Kanakkassery
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=20120724133520.GA19450@x220.ice.intel.com \
--to=johan.hedberg@gmail.com \
--cc=jaganath.k@samsung.com \
--cc=linux-bluetooth@vger.kernel.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).