From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, shuai.zhang@oss.qualcomm.com
Subject: RE: [v1] power: sequencing: qcom-wcn: increase WCN7850 power-up delay
Date: Mon, 02 Nov 2026 11:31:13 -0800 (PST) [thread overview]
Message-ID: <6ae8e501.b52ed58b.308aad.b090@mx.google.com> (raw)
In-Reply-To: <20261102094800.3225454-1-shuai.zhang@oss.qualcomm.com>
[-- Attachment #1: Type: text/plain, Size: 3418 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/1198647/
---Test result---
Test Summary:
CheckPatch PASS 0.50 seconds
VerifyFixes PASS 7.51 seconds
VerifySignedoff PASS 1.27 seconds
GitLint PASS 0.30 seconds
SubjectPrefix FAIL 0.07 seconds
BuildKernel PASS 25.63 seconds
CheckAllWarning PASS 29.05 seconds
CheckSparse PASS 30.66 seconds
BuildKernel32 PASS 25.01 seconds
CheckKernelLLVM PASS 25.07 seconds
TestRunnerSetup PASS 559.75 seconds
TestRunner_l2cap-tester FAIL 12.10 seconds
TestRunner_iso-tester PASS 11.62 seconds
TestRunner_bnep-tester PASS 2.92 seconds
TestRunner_mgmt-tester PASS 83.96 seconds
TestRunner_rfcomm-tester PASS 4.30 seconds
TestRunner_sco-tester PASS 5.10 seconds
TestRunner_ioctl-tester PASS 4.27 seconds
TestRunner_mesh-tester PASS 5.15 seconds
TestRunner_smp-tester PASS 4.23 seconds
TestRunner_userchan-tester PASS 2.88 seconds
TestRunner_6lowpan-tester PASS 4.02 seconds
IncrementalBuild PASS 23.89 seconds
Details
##############################
Test: SubjectPrefix - FAIL
Desc: Check subject contains "Bluetooth" prefix
Output:
"Bluetooth: " prefix is not specified in the subject
##############################
Test: TestRunner_l2cap-tester - FAIL
Desc: Run l2cap-tester with test-runner
Output:
Sanitizer errors:
==35==ERROR: AddressSanitizer: heap-use-after-free on address 0x7b6f351e33d0 at pc 0x561bb9d85e8e bp 0x7ffe98f52c10 sp 0x7ffe98f52c00
READ of size 4 at 0x7b6f351e33d0 thread T0
#0 0x561bb9d85e8d in timeout_callback src/shared/timeout-mainloop.c:33
#1 0x561bb9d86b75 in timeout_callback src/shared/mainloop.c:270
#2 0x561bb9d87aa6 in mainloop_run src/shared/mainloop.c:124
#3 0x561bb9d8a3fa in mainloop_run_with_signal src/shared/mainloop-notify.c:196
#4 0x561bb9d8f64b in tester_run src/shared/tester.c:1223
#5 0x561bb9cb917d in main tools/l2cap-tester.c:3918
#6 0x7f2f361a5600 in __libc_start_call_main ../sysdeps/nptl/libc_start_call_main.h:59
#7 0x7f2f361a5717 in __libc_start_main_impl ../csu/libc-start.c:360
#8 0x561bb9cbfc84 in _start (/home/runner/work/bluetooth-next/bluetooth-next/src/bluez/tools/l2cap-tester+0x16cc84) (BuildId: 91c9d49e9766c394468e27ffa29b05e7d348169f)
0x7b6f351e33d0 is located 0 bytes inside of 40-byte region [0x7b6f351e33d0,0x7b6f351e33f8)
freed by thread T0 here:
#0 0x7f2f36ae33ff in free ../../../../src/libsanitizer/asan/asan_malloc_linux.cpp:51
#1 0x561bb9d8636a in timeout_destroy src/shared/mainloop.c:251
previously allocated by thread T0 here:
#0 0x7f2f36ae460f in malloc ../../../../src/libsanitizer/asan/asan_malloc_linux.cpp:67
#1 0x561bb9d702d5 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/1039
---
Regards,
Linux Bluetooth
next prev parent reply other threads:[~2026-11-02 19:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-02 9:48 [PATCH v1] power: sequencing: qcom-wcn: increase WCN7850 power-up delay Shuai Zhang
2026-11-02 9:59 ` Dmitry Baryshkov
2026-11-02 19:31 ` bluez.test.bot [this message]
2026-11-03 12:29 ` Bartosz Golaszewski
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=6ae8e501.b52ed58b.308aad.b090@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=shuai.zhang@oss.qualcomm.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