public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: Pauli Virtanen <pav@iki.fi>
To: linux-bluetooth@vger.kernel.org
Cc: Pauli Virtanen <pav@iki.fi>
Subject: [PATCH BlueZ v2 0/5] Additional tests for ISO and hci_sync
Date: Tue,  1 Aug 2023 19:38:37 +0300	[thread overview]
Message-ID: <cover.1690907478.git.pav@iki.fi> (raw)

This adds a few tests checking ISO socket handling of invalid input
parameters and cleanup in some race conditions:

    ISO QoS CIG 0xF0 - Invalid
    ISO QoS CIS 0xF0 - Invalid
    ISO Connect2 CIG 0x01 - Success/Invalid
    ISO AC 6(ii) CIS 0xEF/auto - Success
    ISO AC 6(ii) CIS 0xEF/0xEF - Invalid
    ISO Defer Close - Success
    ISO Connect Close - Success
    ISO Defer Wait Close - Success
    ISO Connect Wait Close - Success

There's also one for a hci_sync race condition that triggers GPF:

    eSCO Simultaneous Disconnect - Failure

I have a patch series fixing these, but we'll revisit the
HCI_CONN_DELETED flag there, so maybe discussion needed.

These fail on current bluetooth-next/master, so it could make most sense
to wait for the fixes first.

v2:
- emit correct event from HCI_Create_Connection_Cancel + fix compile

Pauli Virtanen (5):
  btdev: check error conditions for HCI_Create_Connection_Cancel
  btdev: fix Command Status command opcodes for Setup Sync Conn
  sco-tester: test local and remote disconnecting simultaneously
  iso-tester: test with large CIS_ID and invalid CIG_ID/CIS_ID
  iso-tester: add tests checking Remove CIG is emitted

 emulator/btdev.c   |  90 ++++++++++++++++++++----
 monitor/bt.h       |   4 ++
 tools/iso-tester.c | 168 +++++++++++++++++++++++++++++++++++++++++++++
 tools/sco-tester.c |  59 ++++++++++++++++
 4 files changed, 308 insertions(+), 13 deletions(-)

-- 
2.41.0


             reply	other threads:[~2023-08-01 16:38 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-01 16:38 Pauli Virtanen [this message]
2023-08-01 16:38 ` [PATCH BlueZ v2 1/5] btdev: check error conditions for HCI_Create_Connection_Cancel Pauli Virtanen
2023-08-01 18:53   ` Additional tests for ISO and hci_sync bluez.test.bot
2023-08-01 16:38 ` [PATCH BlueZ v2 2/5] btdev: fix Command Status command opcodes for Setup Sync Conn Pauli Virtanen
2023-08-01 16:38 ` [PATCH BlueZ v2 3/5] sco-tester: test local and remote disconnecting simultaneously Pauli Virtanen
2023-08-01 16:38 ` [PATCH BlueZ v2 4/5] iso-tester: test with large CIS_ID and invalid CIG_ID/CIS_ID Pauli Virtanen
2023-08-01 16:38 ` [PATCH BlueZ v2 5/5] iso-tester: add tests checking Remove CIG is emitted Pauli Virtanen
2023-08-04 18:30 ` [PATCH BlueZ v2 0/5] Additional tests for ISO and hci_sync patchwork-bot+bluetooth

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=cover.1690907478.git.pav@iki.fi \
    --to=pav@iki.fi \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox