From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, yfzhang23@stu.pku.edu.cn
Subject: RE: Bluetooth: validate retained LE ISO command lengths
Date: Mon, 02 Nov 2026 11:32:32 -0800 (PST) [thread overview]
Message-ID: <6ae8e550.0c4016f4.1bd57.8ca9@mx.google.com> (raw)
In-Reply-To: <179362071770.29269.17982398081263832695@stu.pku.edu.cn>
[-- Attachment #1: Type: text/plain, Size: 3545 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/1198784/
---Test result---
Test Summary:
CheckPatch PASS 1.37 seconds
VerifyFixes PASS 0.08 seconds
VerifySignedoff PASS 0.09 seconds
GitLint PASS 0.54 seconds
SubjectPrefix PASS 0.16 seconds
BuildKernel PASS 24.95 seconds
CheckAllWarning PASS 28.00 seconds
CheckSparse WARNING 29.42 seconds
BuildKernel32 PASS 24.60 seconds
CheckKernelLLVM PASS 25.20 seconds
TestRunnerSetup PASS 572.25 seconds
TestRunner_l2cap-tester FAIL 11.69 seconds
TestRunner_iso-tester PASS 13.77 seconds
TestRunner_bnep-tester PASS 2.77 seconds
TestRunner_mgmt-tester PASS 84.55 seconds
TestRunner_rfcomm-tester PASS 4.25 seconds
TestRunner_sco-tester PASS 5.08 seconds
TestRunner_ioctl-tester PASS 4.20 seconds
TestRunner_mesh-tester PASS 5.10 seconds
TestRunner_smp-tester PASS 3.98 seconds
TestRunner_userchan-tester PASS 3.41 seconds
TestRunner_6lowpan-tester PASS 4.04 seconds
IncrementalBuild PASS 27.26 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):
##############################
Test: TestRunner_l2cap-tester - FAIL
Desc: Run l2cap-tester with test-runner
Output:
Sanitizer errors:
==35==ERROR: AddressSanitizer: heap-use-after-free on address 0x7bbc644e33d0 at pc 0x55c39ff30e8e bp 0x7ffd38a4a0c0 sp 0x7ffd38a4a0b0
READ of size 4 at 0x7bbc644e33d0 thread T0
#0 0x55c39ff30e8d in timeout_callback src/shared/timeout-mainloop.c:33
#1 0x55c39ff31b75 in timeout_callback src/shared/mainloop.c:270
#2 0x55c39ff32aa6 in mainloop_run src/shared/mainloop.c:124
#3 0x55c39ff353fa in mainloop_run_with_signal src/shared/mainloop-notify.c:196
#4 0x55c39ff3a64b in tester_run src/shared/tester.c:1223
#5 0x55c39fe6417d in main tools/l2cap-tester.c:3918
#6 0x7f7c65443600 in __libc_start_call_main ../sysdeps/nptl/libc_start_call_main.h:59
#7 0x7f7c65443717 in __libc_start_main_impl ../csu/libc-start.c:360
#8 0x55c39fe6ac84 in _start (/home/runner/work/bluetooth-next/bluetooth-next/src/bluez/tools/l2cap-tester+0x16cc84) (BuildId: 91c9d49e9766c394468e27ffa29b05e7d348169f)
0x7bbc644e33d0 is located 0 bytes inside of 40-byte region [0x7bbc644e33d0,0x7bbc644e33f8)
freed by thread T0 here:
#0 0x7f7c65d813ff in free ../../../../src/libsanitizer/asan/asan_malloc_linux.cpp:51
#1 0x55c39ff3136a in timeout_destroy src/shared/mainloop.c:251
previously allocated by thread T0 here:
#0 0x7f7c65d8260f in malloc ../../../../src/libsanitizer/asan/asan_malloc_linux.cpp:67
#1 0x55c39ff1b2d5 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/1041
---
Regards,
Linux Bluetooth
next prev parent reply other threads:[~2026-11-02 19:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-02 11:58 [PATCH 0/2] Bluetooth: validate retained LE ISO command lengths Yifan Zhang
2026-11-02 11:58 ` [PATCH 1/2] Bluetooth: validate retained LE Create CIS command length Yifan Zhang
2026-11-02 19:32 ` bluez.test.bot [this message]
2026-11-02 11:58 ` [PATCH 2/2] Bluetooth: validate retained LE Set CIG Parameters " Yifan Zhang
2026-11-02 22:20 ` [PATCH 0/2] Bluetooth: validate retained LE ISO command lengths 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=6ae8e550.0c4016f4.1bd57.8ca9@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=yfzhang23@stu.pku.edu.cn \
/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