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: Bluetooth: Add support for HDT and EKS
Date: Wed, 04 Nov 2026 14:25:54 -0800 (PST)	[thread overview]
Message-ID: <6aebb0f2.e8a50b02.2bf656.39b0@mx.google.com> (raw)
In-Reply-To: <20261104183626.838825-2-luiz.dentz@gmail.com>

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

---Test result---

Test Summary:
CheckPatch                    PASS      11.82 seconds
VerifyFixes                   PASS      0.09 seconds
VerifySignedoff               PASS      0.11 seconds
GitLint                       PASS      1.45 seconds
SubjectPrefix                 PASS      0.50 seconds
BuildKernel                   PASS      23.62 seconds
CheckAllWarning               PASS      26.76 seconds
CheckSparse                   WARNING   29.42 seconds
BuildKernel32                 PASS      23.60 seconds
CheckKernelLLVM               PASS      24.49 seconds
TestRunnerSetup               PASS      550.35 seconds
TestRunner_l2cap-tester       FAIL      11.84 seconds
TestRunner_iso-tester         PASS      11.55 seconds
TestRunner_bnep-tester        PASS      2.92 seconds
TestRunner_mgmt-tester        PASS      84.37 seconds
TestRunner_rfcomm-tester      PASS      4.09 seconds
TestRunner_sco-tester         PASS      5.18 seconds
TestRunner_ioctl-tester       PASS      4.28 seconds
TestRunner_mesh-tester        PASS      5.15 seconds
TestRunner_smp-tester         PASS      4.03 seconds
TestRunner_userchan-tester    PASS      2.96 seconds
TestRunner_6lowpan-tester     PASS      4.08 seconds
IncrementalBuild              PASS      129.25 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_event.c: note: in included file (through include/net/bluetooth/hci_core.h):net/bluetooth/hci_event.c: note: in included file (through include/net/bluetooth/hci_core.h):net/bluetooth/hci_event.c: note: in included file (through include/net/bluetooth/hci_core.h):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 0x7be44abe33d0 at pc 0x55b3402a4eee bp 0x7ffe04f85de0 sp 0x7ffe04f85dd0
READ of size 4 at 0x7be44abe33d0 thread T0
    #0 0x55b3402a4eed in timeout_callback src/shared/timeout-mainloop.c:33
    #1 0x55b3402a5ed5 in timeout_callback src/shared/mainloop.c:271
    #2 0x55b3402a7006 in mainloop_run src/shared/mainloop.c:125
    #3 0x55b3402a996a in mainloop_run_with_signal src/shared/mainloop-notify.c:196
    #4 0x55b3402aec4b in tester_run src/shared/tester.c:1297
    #5 0x55b3401d81dd in main tools/l2cap-tester.c:3918
    #6 0x7fa44bb91600 in __libc_start_call_main ../sysdeps/nptl/libc_start_call_main.h:59
    #7 0x7fa44bb91717 in __libc_start_main_impl ../csu/libc-start.c:360
    #8 0x55b3401dece4 in _start (/home/runner/work/bluetooth-next/bluetooth-next/src/bluez/tools/l2cap-tester+0x16dce4) (BuildId: 4b6cbb2e2c80ac13520eedc70b7cea5c676c63f3)

0x7be44abe33d0 is located 0 bytes inside of 40-byte region [0x7be44abe33d0,0x7be44abe33f8)
freed by thread T0 here:
    #0 0x7fa44c4cf3ff in free ../../../../src/libsanitizer/asan/asan_malloc_linux.cpp:51
    #1 0x55b3402a53ca in timeout_destroy src/shared/mainloop.c:252

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

---
Regards,
Linux Bluetooth


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

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-04 18:36 [PATCH v2 0/6] Bluetooth: Add support for HDT and EKS Luiz Augusto von Dentz
2026-11-04 18:36 ` [PATCH v2 1/6] Bluetooth: Add initial support for HDT PHY Luiz Augusto von Dentz
2026-11-04 22:25   ` bluez.test.bot [this message]
2026-11-04 18:36 ` [PATCH v2 2/6] Bluetooth: ISO: Add extended QoS with the HDT rates Luiz Augusto von Dentz
2026-11-04 18:36 ` [PATCH v2 3/6] Bluetooth: Add initial support for EKS Luiz Augusto von Dentz
2026-11-04 18:36 ` [PATCH v2 4/6] Bluetooth: L2CAP: Add MIC length validation for HDT PHY Luiz Augusto von Dentz
2026-11-04 18:36 ` [PATCH v2 5/6] Bluetooth: Add HCI_OP_LE_SET_HDT_DEFAULT_PARAMS support Luiz Augusto von Dentz
2026-11-04 18:36 ` [PATCH v2 6/6] Bluetooth: Add EKS Opportunistic Encryption support Luiz Augusto von Dentz

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=6aebb0f2.e8a50b02.2bf656.39b0@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