Linux bluetooth development
 help / color / mirror / Atom feed
From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, luiz.dentz@gmail.com
Subject: RE: [v1,1/6] Bluetooth: Add initial support for HDT PHY
Date: Tue, 03 Nov 2026 18:25:21 -0800 (PST)	[thread overview]
Message-ID: <6aea9791.dd4e4b81.157ef9.5ddd@mx.google.com> (raw)
In-Reply-To: <20261103221921.4071765-3-luiz.dentz@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 6062 bytes --]

This is automated email and please do not reply to this email!

Dear submitter,

Thank you for submitting the patches to the linux bluetooth mailing list.
This is a CI test results with your patch series:
PW Link:https://patchwork.kernel.org/series/1200957/

---Test result---

Test Summary:
CheckPatch                    PASS      3.53 seconds
VerifyFixes                   PASS      0.07 seconds
VerifySignedoff               PASS      0.07 seconds
GitLint                       PASS      0.27 seconds
SubjectPrefix                 PASS      0.07 seconds
BuildKernel                   PASS      32.35 seconds
CheckAllWarning               PASS      38.39 seconds
CheckSparse                   WARNING   40.71 seconds
BuildKernel32                 PASS      32.46 seconds
CheckKernelLLVM               PASS      34.66 seconds
TestRunnerSetup               PASS      765.96 seconds
TestRunner_l2cap-tester       FAIL      10.79 seconds
TestRunner_iso-tester         PASS      11.13 seconds
TestRunner_bnep-tester        PASS      3.17 seconds
TestRunner_mgmt-tester        PASS      89.20 seconds
TestRunner_rfcomm-tester      PASS      4.58 seconds
TestRunner_sco-tester         PASS      5.75 seconds
TestRunner_ioctl-tester       PASS      7.83 seconds
TestRunner_mesh-tester        PASS      5.57 seconds
TestRunner_smp-tester         PASS      4.48 seconds
TestRunner_userchan-tester    PASS      3.29 seconds
TestRunner_6lowpan-tester     PASS      5.09 seconds
IncrementalBuild              PASS      30.61 seconds

Details
##############################
Test: CheckSparse - WARNING
Desc: Run sparse tool with linux kernel
Output:
net/bluetooth/hci_event.c: note: in included file (through include/net/bluetooth/hci_core.h):net/bluetooth/hci_sync.c:8425:42: warning: invalid assignment: |=net/bluetooth/hci_sync.c:8425:42:    left side has type restricted __le16net/bluetooth/hci_sync.c:8425:42:    right side has type unsigned longnet/bluetooth/hci_sync.c:8426:42: warning: invalid assignment: |=net/bluetooth/hci_sync.c:8426:42:    left side has type restricted __le16net/bluetooth/hci_sync.c:8426:42:    right side has type unsigned longnet/bluetooth/hci_sync.c:8427:42: warning: invalid assignment: |=net/bluetooth/hci_sync.c:8427:42:    left side has type restricted __le16net/bluetooth/hci_sync.c:8427:42:    right side has type unsigned longnet/bluetooth/hci_sync.c:8430:50: warning: invalid assignment: |=net/bluetooth/hci_sync.c:8430:50:    left side has type restricted __le16net/bluetooth/hci_sync.c:8430:50:    right side has type unsigned longnet/bluetooth/hci_sync.c:8433:50: warning: invalid assignment: |=net/bluetooth/hci_sync.c:8433:50:    left side has type restricted __le16net/bluetooth/hci_sync.c:8433:50:    right side has type unsigned longnet/bluetooth/hci_sync.c:8437:42: warning: invalid assignment: |=net/bluetooth/hci_sync.c:8437:42:    left side has type restricted __le16net/bluetooth/hci_sync.c:8437:42:    right side has type unsigned longnet/bluetooth/hci_sync.c:8438:42: warning: invalid assignment: |=net/bluetooth/hci_sync.c:8438:42:    left side has type restricted __le16net/bluetooth/hci_sync.c:8438:42:    right side has type unsigned longnet/bluetooth/hci_sync.c:8439:42: warning: invalid assignment: |=net/bluetooth/hci_sync.c:8439:42:    left side has type restricted __le16net/bluetooth/hci_sync.c:8439:42:    right side has type unsigned longnet/bluetooth/hci_sync.c:8442:50: warning: invalid assignment: |=net/bluetooth/hci_sync.c:8442:50:    left side has type restricted __le16net/bluetooth/hci_sync.c:8442:50:    right side has type unsigned longnet/bluetooth/hci_sync.c:8445:50: warning: invalid assignment: |=net/bluetooth/hci_sync.c:8445:50:    left side has type restricted __le16net/bluetooth/hci_sync.c:8445:50:    right side has type unsigned longnet/bluetooth/hci_sync.c:8538:20: warning: incorrect type in assignment (different base types)net/bluetooth/hci_sync.c:8538:20:    expected unsigned short [addressable] [assigned] [usertype] sdunet/bluetooth/hci_sync.c:8538:20:    got restricted __le16 [usertype]net/bluetooth/hci_sync.c:8539:24: warning: incorrect type in assignment (different base types)net/bluetooth/hci_sync.c:8539:24:    expected unsigned short [addressable] [assigned] [usertype] latencynet/bluetooth/hci_sync.c:8539:24:    got restricted __le16 [usertype]
##############################
Test: TestRunner_l2cap-tester - FAIL
Desc: Run l2cap-tester with test-runner
Output:
Sanitizer errors:
==35==ERROR: AddressSanitizer: heap-use-after-free on address 0x7b60767e33d0 at pc 0x55c1c3d0de8e bp 0x7ffe51b1f950 sp 0x7ffe51b1f940
READ of size 4 at 0x7b60767e33d0 thread T0
    #0 0x55c1c3d0de8d in timeout_callback src/shared/timeout-mainloop.c:33
    #1 0x55c1c3d0eb75 in timeout_callback src/shared/mainloop.c:270
    #2 0x55c1c3d0faa6 in mainloop_run src/shared/mainloop.c:124
    #3 0x55c1c3d123fa in mainloop_run_with_signal src/shared/mainloop-notify.c:196
    #4 0x55c1c3d1764b in tester_run src/shared/tester.c:1223
    #5 0x55c1c3c4117d in main tools/l2cap-tester.c:3918
    #6 0x7f207777f600 in __libc_start_call_main ../sysdeps/nptl/libc_start_call_main.h:59
    #7 0x7f207777f717 in __libc_start_main_impl ../csu/libc-start.c:360
    #8 0x55c1c3c47c84 in _start (/home/runner/work/bluetooth-next/bluetooth-next/src/bluez/tools/l2cap-tester+0x16cc84) (BuildId: 91c9d49e9766c394468e27ffa29b05e7d348169f)

0x7b60767e33d0 is located 0 bytes inside of 40-byte region [0x7b60767e33d0,0x7b60767e33f8)
freed by thread T0 here:
    #0 0x7f20780bd3ff in free ../../../../src/libsanitizer/asan/asan_malloc_linux.cpp:51
    #1 0x55c1c3d0e36a in timeout_destroy src/shared/mainloop.c:251

previously allocated by thread T0 here:
    #0 0x7f20780be60f in malloc ../../../../src/libsanitizer/asan/asan_malloc_linux.cpp:67
    #1 0x55c1c3cf82d5 in util_malloc src/shared/util.c:46

SUMMARY: AddressSanitizer: heap-use-after-free src/shared/timeout-mainloop.c:33 in timeout_callback
No test result found


https://github.com/bluez/bluetooth-next/pull/1055

---
Regards,
Linux Bluetooth


  reply	other threads:[~2026-11-04  2:25 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-03 22:19 [GIT PULL] bluetooth 2026-11-02 Luiz Augusto von Dentz
2026-11-03 22:19 ` [PATCH v1 0/6] Bluetooth: Add support for HDT and EKS Luiz Augusto von Dentz
2026-11-03 22:19 ` [PATCH v1 1/6] Bluetooth: Add initial support for HDT PHY Luiz Augusto von Dentz
2026-11-04  2:25   ` bluez.test.bot [this message]
2026-11-03 22:19 ` [PATCH v1 2/6] Bluetooth: ISO: Add new QoS v2 adding rate field Luiz Augusto von Dentz
2026-11-03 22:19 ` [PATCH v1 3/6] Bluetooth: Add initial support for EKS Luiz Augusto von Dentz
2026-11-03 22:19 ` [PATCH v1 4/6] Bluetooth: L2CAP: Add MIC length validation for HDT PHY Luiz Augusto von Dentz
2026-11-03 22:19 ` [PATCH v1 5/6] Bluetooth: Add HCI_OP_LE_SET_HDT_DEFAULT_PARAMS support Luiz Augusto von Dentz
2026-11-03 22:19 ` [PATCH v1 6/6] Bluetooth: Add EKS Opportunistic Encryption support Luiz Augusto von Dentz
2026-11-04  1:48 ` [GIT,PULL] bluetooth 2026-11-02 bluez.test.bot

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=6aea9791.dd4e4b81.157ef9.5ddd@mx.google.com \
    --to=bluez.test.bot@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox