Received-SPF: pass (google.com: domain of linux-bluetooth-owner@vger.kernel.org designates 2620:137:e000::3:8 as permitted sender) client-ip=2620:137:e000::3:8;
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
Subject: Re: [PATCH 1/2] Bluetooth: hci_event: Fix using memcmp when comparing
 keys
From:   patchwork-bot+bluetooth@kernel.org
Message-Id: <169664042376.23949.5642884188872485507.git-patchwork-notify@kernel.org>
Date:   Sat, 07 Oct 2023 01:00:23 +0000
References: <20231005212322.3886919-1-luiz.dentz@gmail.com>
In-Reply-To: <20231005212322.3886919-1-luiz.dentz@gmail.com>
To:     Luiz Augusto von Dentz <luiz.dentz@gmail.com>
Cc:     linux-bluetooth@vger.kernel.org
Precedence: bulk

Hello:

This series was applied to bluetooth/bluetooth-next.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:

On Thu,  5 Oct 2023 14:23:21 -0700 you wrote:
> From: Luiz Augusto von Dentz <luiz.von.dentz@intel.com>
> 
> memcmp is not consider safe to use with cryptographic secrets:
> 
>  'Do  not  use memcmp() to compare security critical data, such as
>  cryptographic secrets, because the required CPU time depends on the
>  number of equal bytes.'
> 
> [...]

Here is the summary with links:
  - [1/2] Bluetooth: hci_event: Fix using memcmp when comparing keys
    https://git.kernel.org/bluetooth/bluetooth-next/c/0ce9e7726323
  - [2/2] Bluetooth: hci_event: Fix coding style
    https://git.kernel.org/bluetooth/bluetooth-next/c/f1b0dea09e3e

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html