Received-SPF: pass (google.com: domain of linux-bluetooth+bounces-872-linux.lists.archive=gmail.com@vger.kernel.org designates 2604:1380:45e3:2400::1 as permitted sender) client-ip=2604:1380:45e3:2400::1;
Content-Type: text/plain; charset="utf-8"
Precedence: bulk
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
Subject: Re: [PATCH BlueZ v2 0/1] mgmt: Fix crash after pair command
From: patchwork-bot+bluetooth@kernel.org
Message-Id: 
 <170431622630.16433.863044364192870086.git-patchwork-notify@kernel.org>
Date: Wed, 03 Jan 2024 21:10:26 +0000
References: <20231219062801.307-1-vinit.mehta@nxp.com>
In-Reply-To: <20231219062801.307-1-vinit.mehta@nxp.com>
To: Vinit Mehta <vinit.mehta@nxp.com>
Cc: linux-bluetooth@vger.kernel.org, devyani.godbole@nxp.com,
 nitin.jadhav@nxp.com

Hello:

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

On Tue, 19 Dec 2023 11:58:00 +0530 you wrote:
> Hello Maintainers
> 
> This patch fixes assertion in bluetoothctl client process
> 
> After pair command, if the user doesn't provide any input on bluetoothctl
> CLI interface after receiving the prompt(yes/no), than subsequent CLI
> command will trigger a call to DBUS library function
> (dbus_message_get_no_reply) with a NULL message pointer which triggers
> assertion in DBUS library causing the bluetoothctl process to crash.
> The change is done in confirm_response callback to trigger a DBUS
> API error call only if the pending_message pointer is not NULL so
> as to avoid the assertion.
> 
> [...]

Here is the summary with links:
  - [BlueZ,v2,1/1] mgmt: Fix crash after pair command
    https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=60d60166e4bf

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