All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+bluetooth@kernel.org
To: Pauli Virtanen <pav@iki.fi>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH BlueZ] main: fix bool vs. gboolean type in g_option_context_parse()
Date: Fri, 05 Dec 2025 15:00:06 +0000	[thread overview]
Message-ID: <176494680629.1671663.485819958976897672.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <36c55de961b5b5ceda83c019ec511f8fa7cd44b6.1764880521.git.pav@iki.fi>

Hello:

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

On Thu,  4 Dec 2025 22:38:09 +0200 you wrote:
> btd_opts.experimental and testing are bool, not gboolean, which may
> cause memory to be clobbered and crash.
> 
> Fix with separate variable for cmdline option.
> 
> Log:
> ERROR: AddressSanitizer: BUS on unknown address
>     #0 0x0000005b9914 in queue_find ../src/shared/queue.c:230
>     #1 0x00000057c0ff in btd_kernel_experimental_enabled ../src/main.c:721
>     #2 0x0000004ff52f in read_exp_features_complete ../src/adapter.c:10230
>     #3 0x0000005be40b in request_complete ../src/shared/mgmt.c:306
> 
> [...]

Here is the summary with links:
  - [BlueZ] main: fix bool vs. gboolean type in g_option_context_parse()
    https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=c42a49a243e4

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



  parent reply	other threads:[~2025-12-05 15:03 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-04 20:38 [PATCH BlueZ] main: fix bool vs. gboolean type in g_option_context_parse() Pauli Virtanen
2025-12-04 21:38 ` [BlueZ] " bluez.test.bot
2025-12-05 15:00 ` patchwork-bot+bluetooth [this message]
2025-12-05 15:13 ` [PATCH BlueZ] " Bastien Nocera
2025-12-05 16:30   ` Pauli Virtanen

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=176494680629.1671663.485819958976897672.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+bluetooth@kernel.org \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=pav@iki.fi \
    /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.