Linux bluetooth development
 help / color / mirror / Atom feed
From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, dev@deq.rocks
Subject: RE: Bluetooth: Broadcom controllers of the Apple T2 Macs
Date: Wed, 04 Nov 2026 08:46:00 -0800 (PST)	[thread overview]
Message-ID: <6aeb6148.e20a777d.27508a.28f5@mx.google.com> (raw)
In-Reply-To: <20261104151601.70493-2-dev@deq.rocks>

[-- Attachment #1: Type: text/plain, Size: 3971 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/1201944/

---Test result---

Test Summary:
CheckPatch                    PASS      17.29 seconds
VerifyFixes                   PASS      0.13 seconds
VerifySignedoff               PASS      0.13 seconds
GitLint                       FAIL      5.05 seconds
SubjectPrefix                 PASS      0.54 seconds
BuildKernel                   PASS      31.31 seconds
CheckAllWarning               PASS      35.69 seconds
CheckSparse                   WARNING   38.56 seconds
BuildKernel32                 PASS      33.61 seconds
CheckKernelLLVM               PASS      35.67 seconds
TestRunnerSetup               PASS      734.75 seconds
TestRunner_l2cap-tester       FAIL      10.66 seconds
TestRunner_iso-tester         PASS      10.73 seconds
TestRunner_bnep-tester        PASS      3.20 seconds
TestRunner_mgmt-tester        PASS      89.37 seconds
TestRunner_rfcomm-tester      PASS      4.51 seconds
TestRunner_sco-tester         PASS      5.75 seconds
TestRunner_ioctl-tester       PASS      4.71 seconds
TestRunner_mesh-tester        PASS      5.59 seconds
TestRunner_smp-tester         PASS      4.41 seconds
TestRunner_userchan-tester    PASS      3.26 seconds
TestRunner_6lowpan-tester     PASS      4.57 seconds
IncrementalBuild              PASS      36.66 seconds

Details
##############################
Test: GitLint - FAIL
Desc: Run gitlint
Output:
[3/4] Revert "Bluetooth: hci_event: strip Broadcom vendor bits from legacy adv report type"

1: T1 Title exceeds max length (91>80): "[3/4] Revert "Bluetooth: hci_event: strip Broadcom vendor bits from legacy adv report type""
[4/4] Bluetooth: set the strict duplicate filter quirk on Apple Broadcom controllers

1: T1 Title exceeds max length (84>80): "[4/4] Bluetooth: set the strict duplicate filter quirk on Apple Broadcom controllers"
##############################
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):
##############################
Test: TestRunner_l2cap-tester - FAIL
Desc: Run l2cap-tester with test-runner
Output:
Sanitizer errors:
==37==ERROR: AddressSanitizer: heap-use-after-free on address 0x7b96372e33d0 at pc 0x562d946f9e8e bp 0x7fffafeca460 sp 0x7fffafeca450
READ of size 4 at 0x7b96372e33d0 thread T0
    #0 0x562d946f9e8d in timeout_callback src/shared/timeout-mainloop.c:33
    #1 0x562d946fab75 in timeout_callback src/shared/mainloop.c:270
    #2 0x562d946fbaa6 in mainloop_run src/shared/mainloop.c:124
    #3 0x562d946fe3fa in mainloop_run_with_signal src/shared/mainloop-notify.c:196
    #4 0x562d9470364b in tester_run src/shared/tester.c:1223
    #5 0x562d9462d17d in main tools/l2cap-tester.c:3918
    #6 0x7f56381c3600 in __libc_start_call_main ../sysdeps/nptl/libc_start_call_main.h:59
    #7 0x7f56381c3717 in __libc_start_main_impl ../csu/libc-start.c:360
    #8 0x562d94633c84 in _start (/home/runner/work/bluetooth-next/bluetooth-next/src/bluez/tools/l2cap-tester+0x16cc84) (BuildId: 91c9d49e9766c394468e27ffa29b05e7d348169f)

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

previously allocated by thread T0 here:
    #0 0x7f5638b0260f in malloc ../../../../src/libsanitizer/asan/asan_malloc_linux.cpp:67
    #1 0x562d946e42d5 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/1065

---
Regards,
Linux Bluetooth


  reply	other threads:[~2026-11-04 16:46 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-04 15:15 [PATCH 0/4] Bluetooth: Broadcom controllers of the Apple T2 Macs Andre Eikmeyer
2026-11-04 15:15 ` [PATCH 1/4] Bluetooth: btbcm: raise ACL priority on Apple Broadcom controllers Andre Eikmeyer
2026-11-04 16:46   ` bluez.test.bot [this message]
2026-11-04 15:15 ` [PATCH 2/4] Bluetooth: btbcm: clear vendor bits in LE advertising report types Andre Eikmeyer
2026-11-04 15:24   ` Luiz Augusto von Dentz
2026-11-04 15:34     ` Aditya Garg
2026-11-04 15:46     ` André Eikmeyer
2026-11-04 16:29       ` Luiz Augusto von Dentz
2026-11-04 16:47         ` André Eikmeyer
2026-11-04 15:16 ` [PATCH 3/4] Revert "Bluetooth: hci_event: strip Broadcom vendor bits from legacy adv report type" Andre Eikmeyer
2026-11-04 15:16 ` [PATCH 4/4] Bluetooth: set the strict duplicate filter quirk on Apple Broadcom controllers Andre Eikmeyer

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=6aeb6148.e20a777d.27508a.28f5@mx.google.com \
    --to=bluez.test.bot@gmail.com \
    --cc=dev@deq.rocks \
    --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