From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, ernesto.salvetti@tambosi.tn.it
Subject: RE: Bluetooth: Fix LE on Barrot 33fa:0010 controllers
Date: Sat, 31 Oct 2026 08:52:03 -0700 (PDT) [thread overview]
Message-ID: <6ae60ea3.e3b8206e.29152d.dcaa@mx.google.com> (raw)
In-Reply-To: <20261031-barrot-le-fixes-v1-v1-1-30e2089882bf@tambosi.tn.it>
[-- Attachment #1: Type: text/plain, Size: 3452 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/1197748/
---Test result---
Test Summary:
CheckPatch PASS 2.73 seconds
VerifyFixes PASS 0.13 seconds
VerifySignedoff PASS 0.13 seconds
GitLint PASS 1.09 seconds
SubjectPrefix PASS 0.37 seconds
BuildKernel PASS 32.02 seconds
CheckAllWarning PASS 39.69 seconds
CheckSparse WARNING 39.28 seconds
BuildKernel32 PASS 31.88 seconds
CheckKernelLLVM PASS 36.79 seconds
TestRunnerSetup PASS 747.97 seconds
TestRunner_l2cap-tester FAIL 12.26 seconds
TestRunner_iso-tester PASS 15.38 seconds
TestRunner_bnep-tester PASS 3.17 seconds
TestRunner_mgmt-tester PASS 88.29 seconds
TestRunner_rfcomm-tester PASS 4.53 seconds
TestRunner_sco-tester PASS 5.67 seconds
TestRunner_ioctl-tester PASS 4.72 seconds
TestRunner_mesh-tester PASS 5.57 seconds
TestRunner_smp-tester PASS 4.39 seconds
TestRunner_userchan-tester PASS 3.25 seconds
TestRunner_6lowpan-tester PASS 4.45 seconds
IncrementalBuild PASS 53.50 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):
##############################
Test: TestRunner_l2cap-tester - FAIL
Desc: Run l2cap-tester with test-runner
Output:
Sanitizer errors:
==36==ERROR: AddressSanitizer: heap-use-after-free on address 0x7b4fc86e33d0 at pc 0x564063e1be8e bp 0x7ffebf4101f0 sp 0x7ffebf4101e0
READ of size 4 at 0x7b4fc86e33d0 thread T0
#0 0x564063e1be8d in timeout_callback src/shared/timeout-mainloop.c:33
#1 0x564063e1cb75 in timeout_callback src/shared/mainloop.c:270
#2 0x564063e1daa6 in mainloop_run src/shared/mainloop.c:124
#3 0x564063e203fa in mainloop_run_with_signal src/shared/mainloop-notify.c:196
#4 0x564063e2564b in tester_run src/shared/tester.c:1223
#5 0x564063d4f17d in main tools/l2cap-tester.c:3918
#6 0x7f0fc9685600 in __libc_start_call_main ../sysdeps/nptl/libc_start_call_main.h:59
#7 0x7f0fc9685717 in __libc_start_main_impl ../csu/libc-start.c:360
#8 0x564063d55c84 in _start (/home/runner/work/bluetooth-next/bluetooth-next/src/bluez/tools/l2cap-tester+0x16cc84) (BuildId: 91c9d49e9766c394468e27ffa29b05e7d348169f)
0x7b4fc86e33d0 is located 0 bytes inside of 40-byte region [0x7b4fc86e33d0,0x7b4fc86e33f8)
freed by thread T0 here:
#0 0x7f0fc9fc33ff in free ../../../../src/libsanitizer/asan/asan_malloc_linux.cpp:51
#1 0x564063e1c36a in timeout_destroy src/shared/mainloop.c:251
previously allocated by thread T0 here:
#0 0x7f0fc9fc460f in malloc ../../../../src/libsanitizer/asan/asan_malloc_linux.cpp:67
#1 0x564063e062d5 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/1035
---
Regards,
Linux Bluetooth
next prev parent reply other threads:[~2026-10-31 15:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-31 12:16 [PATCH 0/3] Bluetooth: Fix LE on Barrot 33fa:0010 controllers Ernesto Salvetti via B4 Relay
2026-10-31 12:16 ` [PATCH 1/3] Bluetooth: hci_core: Don't use extended advertising with broken ext scan Ernesto Salvetti via B4 Relay
2026-10-31 15:52 ` bluez.test.bot [this message]
2026-10-31 12:16 ` [PATCH 2/3] Bluetooth: hci_event: Don't drop LE link on busy remote features read Ernesto Salvetti via B4 Relay
2026-10-31 12:16 ` [PATCH 3/3] Bluetooth: btusb: Disable broken LE extended scan on Barrot controllers Ernesto Salvetti via B4 Relay
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=6ae60ea3.e3b8206e.29152d.dcaa@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=ernesto.salvetti@tambosi.tn.it \
--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