All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+bluetooth@kernel.org
To: Vinit Mehta <vinit.mehta@nxp.com>
Cc: linux-bluetooth@vger.kernel.org, devyani.godbole@nxp.com,
	nitin.jadhav@nxp.com
Subject: Re: [PATCH BlueZ v2 0/1] mgmt: Fix crash after pair command
Date: Wed, 03 Jan 2024 21:10:26 +0000	[thread overview]
Message-ID: <170431622630.16433.863044364192870086.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20231219062801.307-1-vinit.mehta@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



      parent reply	other threads:[~2024-01-03 21:10 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-19  6:28 [PATCH BlueZ v2 0/1] mgmt: Fix crash after pair command Vinit Mehta
2023-12-19  6:28 ` [PATCH BlueZ v2 1/1] " Vinit Mehta
2023-12-19  7:33   ` bluez.test.bot
2024-01-03 21:10 ` patchwork-bot+bluetooth [this message]

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=170431622630.16433.863044364192870086.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+bluetooth@kernel.org \
    --cc=devyani.godbole@nxp.com \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=nitin.jadhav@nxp.com \
    --cc=vinit.mehta@nxp.com \
    /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.