From: Marcel Holtmann <marcel@holtmann.org>
To: Alain Michaud <alainm@chromium.org>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH v4] bluetooth: don't assume key size is 16 when the command fails.
Date: Wed, 25 Mar 2020 15:52:24 +0100 [thread overview]
Message-ID: <53AACEE6-56A0-4D14-AF46-D9AFFF984B2E@holtmann.org> (raw)
In-Reply-To: <20200325144834.207572-1-alainm@chromium.org>
Hi Alain,
> With this change, the encryption key size is not assumed to be 16 if the
> read_encryption_key_size command fails for any reason. This ensures
> that if the controller fails the command for any reason that the
> encryption key size isn't implicitely set to 16 and instead take a more
> concervative posture to assume it is 0.
>
> Signed-off-by: Alain Michaud <alainm@chromium.org>
>
> ---
>
> net/bluetooth/hci_event.c | 8 ++++----
> 1 file changed, 4 insertions(+), 4 deletions(-)
patch has been applied to bluetooth-next tree.
Regards
Marcel
prev parent reply other threads:[~2020-03-25 14:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-25 14:48 [PATCH v4] bluetooth: don't assume key size is 16 when the command fails Alain Michaud
2020-03-25 14:52 ` Marcel Holtmann [this message]
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=53AACEE6-56A0-4D14-AF46-D9AFFF984B2E@holtmann.org \
--to=marcel@holtmann.org \
--cc=alainm@chromium.org \
--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).