Received-SPF: pass (google.com: domain of linux-bluetooth-owner@vger.kernel.org designates 23.128.96.35 as permitted sender) client-ip=23.128.96.35;
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
Subject: Re: [PATCH] [v2] Bluetooth: avoid memcmp() out of bounds warning
From:   patchwork-bot+bluetooth@kernel.org
Message-Id: <169696323071.22645.17463757124543443632.git-patchwork-notify@kernel.org>
Date:   Tue, 10 Oct 2023 18:40:30 +0000
References: <20231009203137.3125516-1-arnd@kernel.org>
In-Reply-To: <20231009203137.3125516-1-arnd@kernel.org>
To:     Arnd Bergmann <arnd@kernel.org>
Cc:     marcel@holtmann.org, johan.hedberg@gmail.com, luiz.dentz@gmail.com,
        jlee@suse.com, arnd@arndb.de, keescook@chromium.org,
        luiz.von.dentz@intel.com, stable@vger.kernel.org,
        iulia.tanasescu@nxp.com, pav@iki.fi, kuba@kernel.org,
        claudia.rosu@nxp.com, linux-bluetooth@vger.kernel.org,
        linux-kernel@vger.kernel.org
Precedence: bulk

Hello:

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

On Mon,  9 Oct 2023 22:31:31 +0200 you wrote:
> From: Arnd Bergmann <arnd@arndb.de>
> 
> bacmp() is a wrapper around memcpy(), which contain compile-time
> checks for buffer overflow. Since the hci_conn_request_evt() also calls
> bt_dev_dbg() with an implicit NULL pointer check, the compiler is now
> aware of a case where 'hdev' is NULL and treats this as meaning that
> zero bytes are available:
> 
> [...]

Here is the summary with links:
  - [v2] Bluetooth: avoid memcmp() out of bounds warning
    https://git.kernel.org/bluetooth/bluetooth-next/c/b8ba8e65e84b

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