All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Hans-Christian Egtvedt (hegtvedt)" <hegtvedt@cisco.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"Luiz Augusto von Dentz" <luiz.von.dentz@intel.com>,
	Marcel Holtmann <marcel@holtmann.org>
Subject: Re: [PATCH v4.4/bluetooth 1/2] Bluetooth: Consolidate encryption handling in hci_encrypt_cfm
Date: Thu, 15 Oct 2020 11:18:39 +0000	[thread overview]
Message-ID: <0804be81-ebbf-8132-a619-c0c740a71f51@cisco.com> (raw)
In-Reply-To: <20201015095750.GA3935178@kroah.com>

[-- Attachment #1: Type: text/plain, Size: 1836 bytes --]

On 15/10/2020 11:57, Greg KH wrote:
> On Thu, Oct 15, 2020 at 09:43:32AM +0200, Hans-Christian Noren Egtvedt wrote:
>> From: Luiz Augusto von Dentz <luiz.von.dentz@intel.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@intel.com>
>> Signed-off-by: Marcel Holtmann <marcel@holtmann.org>
>> (cherry picked from commit 3ca44c16b0dcc764b641ee4ac226909f5c421aa3)
> 
> This is only in 5.8, what about all the other stable kernels?
> 
>> (cherry picked from commit 0a60996c7fa7010ea00d9b62fb6996d908a01ead)
> 
> Where is this commit from?  I don't see it in Linus's tree.

Ops, my bad, I have a Linux 4.9 branch, which also includes the Android
4.9 kernel changes from Google. And since I noticed the patches in my
(merged from Android latest) linux-4.9.y branch, I thought the patches
were applied through all stable releases 4.9 and up.

>> ---
>> AFAICT, fixing CVE 2020-10135 Bluetooth impersonation attacks have been
>> left out for the 4.4 stable kernel. I cherry picked what I assume are
>> the appropriate two patches missing from the 4.9 stable kernel. Please
>> add them to upcoming 4.4 stable releases.
> 
> Why are you merging 2 commits together?  Please provide backports for
> all stable kernels, if you want to see this in the 4.4.y tree.  We can
> not have someone move from an older tree to a newer one and have a
> regression.

Agreed, I have managed to trick myself into thinking the 4.4.y branch
was left out, but I assume these patches are required for all LTS branches.

That is a bigger job AFAIK, the newer branches might need additional
patches. Perhaps Luiz can assist?

-- 
Best regards, Hans-Christian Noren Egtvedt

[-- Attachment #2: pEpkey.asc --]
[-- Type: application/pgp-keys, Size: 1813 bytes --]

  reply	other threads:[~2020-10-15 11:27 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-15  7:43 [PATCH v4.4/bluetooth 1/2] Bluetooth: Consolidate encryption handling in hci_encrypt_cfm Hans-Christian Noren Egtvedt
2020-10-15  7:43 ` [PATCH v4.4/bluetooth 2/2] Bluetooth: Disconnect if E0 is used for Level 4 Hans-Christian Noren Egtvedt
2020-10-15  9:58   ` Greg KH
2020-10-15  9:57 ` [PATCH v4.4/bluetooth 1/2] Bluetooth: Consolidate encryption handling in hci_encrypt_cfm Greg KH
2020-10-15 11:18   ` Hans-Christian Egtvedt (hegtvedt) [this message]
2020-10-15 12:02     ` Greg KH
2020-10-15 12:44       ` Hans-Christian Egtvedt (hegtvedt)
2020-10-15 21:15         ` Hans-Christian Egtvedt (hegtvedt)

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=0804be81-ebbf-8132-a619-c0c740a71f51@cisco.com \
    --to=hegtvedt@cisco.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luiz.von.dentz@intel.com \
    --cc=marcel@holtmann.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.