All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pauli Virtanen <noreply@github.com>
To: linux-bluetooth@vger.kernel.org
Subject: [bluez/bluez] ace43b: emulator: bthost: add function for sending raw L2C...
Date: Sun, 30 Aug 2026 11:24:39 -0700	[thread overview]
Message-ID: <bluez/bluez/push/refs/heads/1153956/000000-6f01a4@github.com> (raw)

  Branch: refs/heads/1153956
  Home:   https://github.com/bluez/bluez
  Commit: ace43bd022cd4fc18d065e06421f196f89afeaf3
      https://github.com/bluez/bluez/commit/ace43bd022cd4fc18d065e06421f196f89afeaf3
  Author: Pauli Virtanen <pav@iki.fi>
  Date:   2026-08-30 (Sun, 30 Aug 2026)

  Changed paths:
    M emulator/bthost.c
    M emulator/bthost.h

  Log Message:
  -----------
  emulator: bthost: add function for sending raw L2CAP sig commands

Add bthost_l2cap_sig_raw() that tests can use to send raw L2CAP
signaling commands.


  Commit: 6f01a45f06cbce1e14bee0ab241358a10954da4e
      https://github.com/bluez/bluez/commit/6f01a45f06cbce1e14bee0ab241358a10954da4e
  Author: Pauli Virtanen <pav@iki.fi>
  Date:   2026-08-30 (Sun, 30 Aug 2026)

  Changed paths:
    M tools/l2cap-tester.c

  Log Message:
  -----------
  tools/l2cap-server: add test for invalid Conn Req on Ext-Flowctl server

Add test that checks Ext-Flowctl server handles invalid connection
requests with ident collisions. This triggers null-deref crash / hang on
some kernel versions.

L2CAP Ext-Flowctl Server - Nval Conn Req


Compare: https://github.com/bluez/bluez/compare/ace43bd022cd%5E...6f01a45f06cb

To unsubscribe from these emails, change your notification settings at https://github.com/bluez/bluez/settings/notifications

                 reply	other threads:[~2026-08-30 18:24 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=bluez/bluez/push/refs/heads/1153956/000000-6f01a4@github.com \
    --to=noreply@github.com \
    --cc=linux-bluetooth@vger.kernel.org \
    /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.