linux-kernel - Re: [v4.4/bluetooth PATCH 1/3] Bluetooth: Consolidate encryption handling in hci_encrypt

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:   Fri, 16 Oct 2020 09:54:55 +0200
From:   Greg KH <gregkh@...uxfoundation.org>
To:     "Hans-Christian Egtvedt (hegtvedt)" <hegtvedt@...co.com>
Cc:     "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
        Luiz Augusto von Dentz <luiz.von.dentz@...el.com>,
        Marcel Holtmann <marcel@...tmann.org>,
        "stable@...r.kernel.org" <stable@...r.kernel.org>
Subject: Re: [v4.4/bluetooth PATCH 1/3] Bluetooth: Consolidate encryption
 handling in hci_encrypt_cfm

On Fri, Oct 16, 2020 at 07:46:39AM +0000, Hans-Christian Egtvedt (hegtvedt) wrote:
> On 16/10/2020 09:32, Greg KH wrote:
> > On Thu, Oct 15, 2020 at 11:12:23PM +0200, Hans-Christian Noren Egtvedt wrote:
> >> From: Luiz Augusto von Dentz <luiz.von.dentz@...el.com>
> >>
> >> This makes hci_encrypt_cfm calls hci_connect_cfm in case the connection
> >> state is BT_CONFIG so callers don't have to check the state.
> >>
> >> Signed-off-by: Luiz Augusto von Dentz <luiz.von.dentz@...el.com>
> >> Signed-off-by: Marcel Holtmann <marcel@...tmann.org>
> >> (cherry picked from commit 3ca44c16b0dcc764b641ee4ac226909f5c421aa3)
> >> Cc: stable@...r.kernel.org # 4.4
> >> ---
> >>  include/net/bluetooth/hci_core.h | 20 ++++++++++++++++++--
> >>  net/bluetooth/hci_event.c        | 28 +++-------------------------
> >>  2 files changed, 21 insertions(+), 27 deletions(-)
> > 
> > What differs here from the other patch series you sent?  Looks the same
> > to me...
> 
> Patch 1 and 2 in this series is identical, patch 3/3 is adjusted to
> resolve a conflict. Sorry I did not make that clearer.

No problem, thanks for confirming this, that makes me feel better that I
didn't miss anything.

greg k-h