From: Marcel Holtmann <marcel@holtmann.org>
To: Johan Hedberg <johan.hedberg@gmail.com>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH] Bluetooth: Fix locking of hdev when calling into SMP code
Date: Fri, 13 Jun 2014 11:18:38 +0200 [thread overview]
Message-ID: <635EF99A-0301-470A-898C-757799A084E8@holtmann.org> (raw)
In-Reply-To: <1402644148-24141-1-git-send-email-johan.hedberg@gmail.com>
Hi Johan,
> The SMP code expects hdev to be unlocked since e.g. crypto functions
> will try to (re)lock it. Therefore, we need to release the lock before
> calling into smp.c from mgmt.c. Without this we risk a deadlock whenever
> the smp_user_confirm_reply() function is called.
>
> Signed-off-by: Johan Hedberg <johan.hedberg@intel.com>
> ---
> net/bluetooth/mgmt.c | 7 ++++++-
> 1 file changed, 6 insertions(+), 1 deletion(-)
>
> diff --git a/net/bluetooth/mgmt.c b/net/bluetooth/mgmt.c
> index 6107e037cd8e..af8e0a6243b7 100644
> --- a/net/bluetooth/mgmt.c
> +++ b/net/bluetooth/mgmt.c
> @@ -3031,8 +3031,13 @@ static int user_pairing_resp(struct sock *sk, struct hci_dev *hdev,
> }
>
> if (addr->type == BDADDR_LE_PUBLIC || addr->type == BDADDR_LE_RANDOM) {
> - /* Continue with pairing via SMP */
> + /* Continue with pairing via SMP. The hdev lock must be
> + * released as SMP may try to recquire it for crypto
> + * purposes.
> + */
> + hci_dev_unlock(hdev);
> err = smp_user_confirm_reply(conn, mgmt_op, passkey);
> + hci_dev_lock(hdev);
providing a __smp_user_confirm_reply that operates on a locked hdev and where the crypto functions do not take the hdev lock is not possible.
The lock/unlock seems a bit counterproductive here.
Regards
Marcel
next prev parent reply other threads:[~2014-06-13 9:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-13 7:22 [PATCH] Bluetooth: Fix locking of hdev when calling into SMP code johan.hedberg
2014-06-13 7:42 ` Lukasz Rymanowski
2014-06-13 9:18 ` Marcel Holtmann [this message]
2014-06-13 11:18 ` Marcel Holtmann
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=635EF99A-0301-470A-898C-757799A084E8@holtmann.org \
--to=marcel@holtmann.org \
--cc=johan.hedberg@gmail.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 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.