From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, zzzccc427@gmail.com
Subject: RE: Bluetooth: Fix advertising instance accesses without hdev->lock
Date: Fri, 30 Oct 2026 09:45:22 -0700 (PDT) [thread overview]
Message-ID: <6ae4c9a2.5a092a7f.18d9eb.fd21@mx.google.com> (raw)
In-Reply-To: <pm-bluetooth-objects-candidate-0245-v9-6b34bc036455ad3dd4ea-1@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 3251 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/1197214/
---Test result---
Test Summary:
CheckPatch PASS 2.33 seconds
VerifyFixes PASS 0.13 seconds
VerifySignedoff PASS 0.13 seconds
GitLint PASS 1.20 seconds
SubjectPrefix PASS 0.35 seconds
BuildKernel PASS 32.04 seconds
CheckAllWarning PASS 38.53 seconds
CheckSparse PASS 38.36 seconds
BuildKernel32 PASS 31.19 seconds
CheckKernelLLVM PASS 33.38 seconds
TestRunnerSetup PASS 744.07 seconds
TestRunner_l2cap-tester FAIL 12.26 seconds
TestRunner_iso-tester PASS 10.88 seconds
TestRunner_bnep-tester PASS 3.17 seconds
TestRunner_mgmt-tester PASS 88.75 seconds
TestRunner_rfcomm-tester PASS 4.54 seconds
TestRunner_sco-tester PASS 5.70 seconds
TestRunner_ioctl-tester PASS 4.72 seconds
TestRunner_mesh-tester PASS 5.59 seconds
TestRunner_smp-tester PASS 4.42 seconds
TestRunner_userchan-tester PASS 3.77 seconds
TestRunner_6lowpan-tester PASS 4.47 seconds
IncrementalBuild PASS 33.64 seconds
Details
##############################
Test: TestRunner_l2cap-tester - FAIL
Desc: Run l2cap-tester with test-runner
Output:
Sanitizer errors:
==35==ERROR: AddressSanitizer: heap-use-after-free on address 0x7c0212ee33d0 at pc 0x560ef2fa5e8e bp 0x7ffc4e083ff0 sp 0x7ffc4e083fe0
READ of size 4 at 0x7c0212ee33d0 thread T0
#0 0x560ef2fa5e8d in timeout_callback src/shared/timeout-mainloop.c:33
#1 0x560ef2fa6b75 in timeout_callback src/shared/mainloop.c:270
#2 0x560ef2fa7aa6 in mainloop_run src/shared/mainloop.c:124
#3 0x560ef2faa3fa in mainloop_run_with_signal src/shared/mainloop-notify.c:196
#4 0x560ef2faf64b in tester_run src/shared/tester.c:1223
#5 0x560ef2ed917d in main tools/l2cap-tester.c:3918
#6 0x7fc213e7d600 in __libc_start_call_main ../sysdeps/nptl/libc_start_call_main.h:59
#7 0x7fc213e7d717 in __libc_start_main_impl ../csu/libc-start.c:360
#8 0x560ef2edfc84 in _start (/home/runner/work/bluetooth-next/bluetooth-next/src/bluez/tools/l2cap-tester+0x16cc84) (BuildId: 91c9d49e9766c394468e27ffa29b05e7d348169f)
0x7c0212ee33d0 is located 0 bytes inside of 40-byte region [0x7c0212ee33d0,0x7c0212ee33f8)
freed by thread T0 here:
#0 0x7fc2147bb3ff in free ../../../../src/libsanitizer/asan/asan_malloc_linux.cpp:51
#1 0x560ef2fa636a in timeout_destroy src/shared/mainloop.c:251
previously allocated by thread T0 here:
#0 0x7fc2147bc60f in malloc ../../../../src/libsanitizer/asan/asan_malloc_linux.cpp:67
#1 0x560ef2f902d5 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/1031
---
Regards,
Linux Bluetooth
next prev parent reply other threads:[~2026-10-30 16:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-30 14:27 [PATCH 0/2] Bluetooth: Fix advertising instance accesses without hdev->lock Cen Zhang
2026-10-30 14:27 ` [PATCH 1/2] Bluetooth: hci_sync: Fix remaining advertising instance UAFs Cen Zhang
2026-10-30 16:45 ` bluez.test.bot [this message]
2026-10-30 14:27 ` [PATCH 2/2] Bluetooth: hci_core: Initialize advertising RPA work only once Cen Zhang
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=6ae4c9a2.5a092a7f.18d9eb.fd21@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox