From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, luiz.dentz@gmail.com
Subject: RE: [v1] Bluetooth: Fix not updating of hdev->commands[] after reset
Date: Wed, 04 Nov 2026 18:44:19 -0800 (PST) [thread overview]
Message-ID: <6aebed83.54e42a5c.246e68.763c@mx.google.com> (raw)
In-Reply-To: <20261104221956.1207025-1-luiz.dentz@gmail.com>
[-- 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/1202519/
---Test result---
Test Summary:
CheckPatch PASS 0.59 seconds
VerifyFixes PASS 0.07 seconds
VerifySignedoff PASS 0.07 seconds
GitLint PASS 0.22 seconds
SubjectPrefix PASS 0.07 seconds
BuildKernel PASS 31.38 seconds
CheckAllWarning PASS 35.58 seconds
CheckSparse WARNING 38.36 seconds
BuildKernel32 PASS 30.73 seconds
CheckKernelLLVM PASS 33.06 seconds
TestRunnerSetup PASS 742.14 seconds
TestRunner_l2cap-tester FAIL 10.67 seconds
TestRunner_iso-tester PASS 21.63 seconds
TestRunner_bnep-tester PASS 9.66 seconds
TestRunner_mgmt-tester PASS 88.22 seconds
TestRunner_rfcomm-tester PASS 4.47 seconds
TestRunner_sco-tester PASS 5.63 seconds
TestRunner_ioctl-tester PASS 4.65 seconds
TestRunner_mesh-tester PASS 5.53 seconds
TestRunner_smp-tester PASS 4.36 seconds
TestRunner_userchan-tester PASS 3.21 seconds
TestRunner_6lowpan-tester PASS 4.42 seconds
IncrementalBuild PASS 29.12 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:
==35==ERROR: AddressSanitizer: heap-use-after-free on address 0x7b69e63e33d0 at pc 0x564e45f78eee bp 0x7ffd6db81ef0 sp 0x7ffd6db81ee0
READ of size 4 at 0x7b69e63e33d0 thread T0
#0 0x564e45f78eed in timeout_callback src/shared/timeout-mainloop.c:33
#1 0x564e45f79ed5 in timeout_callback src/shared/mainloop.c:271
#2 0x564e45f7b006 in mainloop_run src/shared/mainloop.c:125
#3 0x564e45f7d96a in mainloop_run_with_signal src/shared/mainloop-notify.c:196
#4 0x564e45f82c4b in tester_run src/shared/tester.c:1297
#5 0x564e45eac1dd in main tools/l2cap-tester.c:3918
#6 0x7f29e7387600 in __libc_start_call_main ../sysdeps/nptl/libc_start_call_main.h:59
#7 0x7f29e7387717 in __libc_start_main_impl ../csu/libc-start.c:360
#8 0x564e45eb2ce4 in _start (/home/runner/work/bluetooth-next/bluetooth-next/src/bluez/tools/l2cap-tester+0x16dce4) (BuildId: 4b6cbb2e2c80ac13520eedc70b7cea5c676c63f3)
0x7b69e63e33d0 is located 0 bytes inside of 40-byte region [0x7b69e63e33d0,0x7b69e63e33f8)
freed by thread T0 here:
#0 0x7f29e7cc53ff in free ../../../../src/libsanitizer/asan/asan_malloc_linux.cpp:51
#1 0x564e45f793ca in timeout_destroy src/shared/mainloop.c:252
previously allocated by thread T0 here:
#0 0x7f29e7cc660f in malloc ../../../../src/libsanitizer/asan/asan_malloc_linux.cpp:67
#1 0x564e45f63335 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/1068
---
Regards,
Linux Bluetooth
next prev parent reply other threads:[~2026-11-05 2:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-04 22:19 [PATCH v1] Bluetooth: Fix not updating of hdev->commands[] after reset Luiz Augusto von Dentz
2026-11-05 2:44 ` bluez.test.bot [this message]
2026-11-05 16:32 ` 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=6aebed83.54e42a5c.246e68.763c@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