All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marek Szyprowski <m.szyprowski@samsung.com>
To: Luiz Augusto von Dentz <luiz.dentz@gmail.com>
Cc: "linux-bluetooth@vger.kernel.org" <linux-bluetooth@vger.kernel.org>
Subject: Re: [PATCH v7 2/7] Bluetooth: Add initial implementation of CIS connections
Date: Wed, 10 Aug 2022 16:18:24 +0200	[thread overview]
Message-ID: <03f9bea9-77fb-2b57-43d0-c4b819c2560a@samsung.com> (raw)
In-Reply-To: <CABBYNZLsR0KT1-OVVjnUzLp0+U0eHGi0PNqKbfntp_5AHNDawA@mail.gmail.com>

Hi Luiz,

On 09.08.2022 21:24, Luiz Augusto von Dentz wrote:
> On Tue, Aug 9, 2022 at 1:55 AM Marek Szyprowski
> <m.szyprowski@samsung.com>  wrote:
>> On 12.07.2022 01:35, Luiz Augusto von Dentz wrote:
>>> From: Luiz Augusto von Dentz<luiz.von.dentz@intel.com>
>>>
>>> This adds the initial implementation of CIS connections and introduces
>>> the ISO packets/links.
>>>
>>> == Central: Set CIG Parameters, create a CIS and Setup Data Path ==
>>>
>>>> tools/isotest -s <address>
>>> < HCI Command: LE Extended Create... (0x08|0x0043) plen 26
>>> ...
>>>> HCI Event: Command Status (0x0f) plen 4
>>>         LE Extended Create Connection (0x08|0x0043) ncmd 1
>>>           Status: Success (0x00)
>>>> HCI Event: LE Meta Event (0x3e) plen 31
>>>         LE Enhanced Connection Complete (0x0a)
>>>         ...
>>> < HCI Command: LE Create Connected... (0x08|0x0064) plen 5
>>> ...
>>>> HCI Event: Command Status (0x0f) plen 4
>>>         LE Create Connected Isochronous Stream (0x08|0x0064) ncmd 1
>>>           Status: Success (0x00)
>>>> HCI Event: LE Meta Event (0x3e) plen 29
>>>         LE Connected Isochronous Stream Established (0x19)
>>>         ...
>>> < HCI Command: LE Setup Isochronou.. (0x08|0x006e) plen 13
>>> ...
>>>> HCI Event: Command Complete (0x0e) plen 6
>>>         LE Setup Isochronous Data Path (0x08|0x006e) ncmd 1
>>>           Status: Success (0x00)
>>>           Handle: 257
>>> < HCI Command: LE Setup Isochronou.. (0x08|0x006e) plen 13
>>> ...
>>>> HCI Event: Command Complete (0x0e) plen 6
>>>         LE Setup Isochronous Data Path (0x08|0x006e) ncmd 1
>>>           Status: Success (0x00)
>>>           Handle: 257
>>>
>>> == Peripheral: Accept CIS and Setup Data Path ==
>>>
>>>> tools/isotest -d
>>>    HCI Event: LE Meta Event (0x3e) plen 7
>>>         LE Connected Isochronous Stream Request (0x1a)
>>> ...
>>> < HCI Command: LE Accept Co.. (0x08|0x0066) plen 2
>>> ...
>>>> HCI Event: LE Meta Event (0x3e) plen 29
>>>         LE Connected Isochronous Stream Established (0x19)
>>> ...
>>> < HCI Command: LE Setup Is.. (0x08|0x006e) plen 13
>>> ...
>>>> HCI Event: Command Complete (0x0e) plen 6
>>>         LE Setup Isochronous Data Path (0x08|0x006e) ncmd 1
>>>           Status: Success (0x00)
>>>           Handle: 257
>>> < HCI Command: LE Setup Is.. (0x08|0x006e) plen 13
>>> ...
>>>> HCI Event: Command Complete (0x0e) plen 6
>>>         LE Setup Isochronous Data Path (0x08|0x006e) ncmd 1
>>>           Status: Success (0x00)
>>>           Handle: 257
>>>
>>> Signed-off-by: Luiz Augusto von Dentz<luiz.von.dentz@intel.com>
>> This patch landed recently in linux-next as commit 26afbd826ee3
>> ("Bluetooth: Add initial implementation of CIS connections").
>> Unfortunately it causes a regression on my test systems. On almost all
>> I've observed that calling a simple 'hcitool scan' command in a shell
>> fails in an unexpected way:
>>
>> $ hcitool scan
>> *** stack smashing detected ***: <unknown> terminated
>> Aborted
> Not really sure how it would be related to ISO changes though, have
> you even enabled ISO sockets UUID? Perhaps check if there is something
> on dmesg indicating what is going on since I tried here and that
> doesn't seem to cause any problem:
>
> tools/hcitool scan
> Scanning ...
>
> Perhaps it is a combination of using old userspace tools with new
> kernel, but then again these changes should affect something like
> hcitool.

Indeed my userspace is old, but still, the kernel changes shouldn't make 
it to crash. I didn't change anything in userspace since ages, so I 
assume that ISO sockets UUIDs are not enabled. Maybe it is somehow 
architecture related or specific? It looks that only ARM 32bit userspace 
apps crashes. I've just checked 64bit userspace on ARM64 (RPi4) and it 
works fine with that commit.

Best regards
-- 
Marek Szyprowski, PhD
Samsung R&D Institute Poland


  reply	other threads:[~2022-08-10 14:18 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-11 23:35 [PATCH v7 1/7] Bluetooth: hci_core: Introduce hci_recv_event_data Luiz Augusto von Dentz
2022-07-11 23:35 ` [PATCH v7 2/7] Bluetooth: Add initial implementation of CIS connections Luiz Augusto von Dentz
     [not found]   ` <CGME20220809085500eucas1p18cb2752164ca55832787e7d3843f48ab@eucas1p1.samsung.com>
2022-08-09  8:54     ` Marek Szyprowski
2022-08-09 19:24       ` Luiz Augusto von Dentz
2022-08-10 14:18         ` Marek Szyprowski [this message]
2022-08-10 20:04           ` Luiz Augusto von Dentz
2022-08-12 12:33             ` Marek Szyprowski
2022-08-16 15:24               ` Marek Szyprowski
2022-09-08 10:25                 ` Marek Szyprowski
2022-09-08 15:25                   ` Luiz Augusto von Dentz
2022-07-11 23:35 ` [PATCH v7 3/7] Bluetooth: Add BTPROTO_ISO socket type Luiz Augusto von Dentz
2022-07-11 23:35 ` [PATCH v7 4/7] Bluetooth: Add initial implementation of BIS connections Luiz Augusto von Dentz
2022-07-11 23:35 ` [PATCH v7 5/7] Bluetooth: ISO: Add broadcast support Luiz Augusto von Dentz
2022-07-11 23:35 ` [PATCH v7 6/7] Bluetooth: btusb: Add support for ISO packets Luiz Augusto von Dentz
2022-07-11 23:35 ` [PATCH v7 7/7] Bluetooth: btusb: Detect if an ACL packet is in fact an ISO packet Luiz Augusto von Dentz
2022-07-12  0:01 ` [v7,1/7] Bluetooth: hci_core: Introduce hci_recv_event_data bluez.test.bot
2022-07-22 20:40 ` [PATCH v7 1/7] " 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=03f9bea9-77fb-2b57-43d0-c4b819c2560a@samsung.com \
    --to=m.szyprowski@samsung.com \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=luiz.dentz@gmail.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.