From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, zzzccc427@gmail.com
Subject: RE: Bluetooth: SMP: Serialize root channel updates
Date: Sat, 31 Oct 2026 02:44:42 -0700 (PDT) [thread overview]
Message-ID: <6ae5b88a.b97a138d.f69dd.b2e8@mx.google.com> (raw)
In-Reply-To: <pm-bluetooth-objects-candidate-0184-v9-4094fa28af7bd56a283a-1@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 3253 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/1197650/
---Test result---
Test Summary:
CheckPatch PASS 2.45 seconds
VerifyFixes PASS 0.09 seconds
VerifySignedoff PASS 0.09 seconds
GitLint PASS 0.90 seconds
SubjectPrefix PASS 0.29 seconds
BuildKernel PASS 31.20 seconds
CheckAllWarning PASS 36.35 seconds
CheckSparse PASS 39.24 seconds
BuildKernel32 PASS 31.90 seconds
CheckKernelLLVM PASS 34.91 seconds
TestRunnerSetup PASS 724.30 seconds
TestRunner_l2cap-tester FAIL 10.55 seconds
TestRunner_iso-tester PASS 10.79 seconds
TestRunner_bnep-tester PASS 3.16 seconds
TestRunner_mgmt-tester PASS 87.61 seconds
TestRunner_rfcomm-tester PASS 11.94 seconds
TestRunner_sco-tester PASS 5.60 seconds
TestRunner_ioctl-tester PASS 4.63 seconds
TestRunner_mesh-tester PASS 5.53 seconds
TestRunner_smp-tester PASS 10.36 seconds
TestRunner_userchan-tester PASS 3.21 seconds
TestRunner_6lowpan-tester PASS 4.44 seconds
IncrementalBuild PASS 35.53 seconds
Details
##############################
Test: TestRunner_l2cap-tester - FAIL
Desc: Run l2cap-tester with test-runner
Output:
Sanitizer errors:
==37==ERROR: AddressSanitizer: heap-use-after-free on address 0x7c21733e33d0 at pc 0x559ed80ece8e bp 0x7ffed3ea2520 sp 0x7ffed3ea2510
READ of size 4 at 0x7c21733e33d0 thread T0
#0 0x559ed80ece8d in timeout_callback src/shared/timeout-mainloop.c:33
#1 0x559ed80edb75 in timeout_callback src/shared/mainloop.c:270
#2 0x559ed80eeaa6 in mainloop_run src/shared/mainloop.c:124
#3 0x559ed80f13fa in mainloop_run_with_signal src/shared/mainloop-notify.c:196
#4 0x559ed80f664b in tester_run src/shared/tester.c:1223
#5 0x559ed802017d in main tools/l2cap-tester.c:3918
#6 0x7fe17438b600 in __libc_start_call_main ../sysdeps/nptl/libc_start_call_main.h:59
#7 0x7fe17438b717 in __libc_start_main_impl ../csu/libc-start.c:360
#8 0x559ed8026c84 in _start (/home/runner/work/bluetooth-next/bluetooth-next/src/bluez/tools/l2cap-tester+0x16cc84) (BuildId: 91c9d49e9766c394468e27ffa29b05e7d348169f)
0x7c21733e33d0 is located 0 bytes inside of 40-byte region [0x7c21733e33d0,0x7c21733e33f8)
freed by thread T0 here:
#0 0x7fe174cc93ff in free ../../../../src/libsanitizer/asan/asan_malloc_linux.cpp:51
#1 0x559ed80ed36a in timeout_destroy src/shared/mainloop.c:251
previously allocated by thread T0 here:
#0 0x7fe174cca60f in malloc ../../../../src/libsanitizer/asan/asan_malloc_linux.cpp:67
#1 0x559ed80d72d5 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/1034
---
Regards,
Linux Bluetooth
next prev parent reply other threads:[~2026-10-31 9:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-31 7:32 [PATCH v3 0/3] Bluetooth: SMP: Serialize root channel updates Cen Zhang
2026-10-31 7:32 ` [PATCH v3 1/3] Bluetooth: SMP: Serialize forced BR/EDR channel changes Cen Zhang
2026-10-31 9:44 ` bluez.test.bot [this message]
2026-10-31 7:32 ` [PATCH v3 2/3] Bluetooth: hci_core: Hold the request lock for the power-on update Cen Zhang
2026-10-31 7:32 ` [PATCH v3 3/3] Bluetooth: SMP: Serialize root channel replacement Cen Zhang
-- strict thread matches above, loose matches on Subject: below --
2026-10-30 14:43 [PATCH 1/2] Bluetooth: SMP: Serialize forced BR/EDR channel changes Cen Zhang
2026-10-30 16:41 ` Bluetooth: SMP: Serialize root channel updates 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=6ae5b88a.b97a138d.f69dd.b2e8@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=zzzccc427@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.