From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, vulab@iscas.ac.cn
Subject: RE: Bluetooth: delete the new SCO link if linking it fails
Date: Wed, 04 Nov 2026 00:46:05 -0800 (PST) [thread overview]
Message-ID: <6aeaf0cd.6510e82a.12e6b9.fc61@mx.google.com> (raw)
In-Reply-To: <20261104022807.1484114-1-vulab@iscas.ac.cn>
[-- Attachment #1: Type: text/plain, Size: 4119 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/1201153/
---Test result---
Test Summary:
CheckPatch FAIL 0.75 seconds
VerifyFixes PASS 0.12 seconds
VerifySignedoff PASS 0.12 seconds
GitLint PASS 0.32 seconds
SubjectPrefix PASS 0.11 seconds
BuildKernel PASS 31.42 seconds
CheckAllWarning PASS 35.06 seconds
CheckSparse PASS 38.07 seconds
BuildKernel32 PASS 30.88 seconds
CheckKernelLLVM PASS 35.24 seconds
TestRunnerSetup PASS 745.30 seconds
TestRunner_l2cap-tester FAIL 10.73 seconds
TestRunner_iso-tester PASS 10.87 seconds
TestRunner_bnep-tester PASS 3.21 seconds
TestRunner_mgmt-tester PASS 91.90 seconds
TestRunner_rfcomm-tester PASS 4.63 seconds
TestRunner_sco-tester PASS 5.66 seconds
TestRunner_ioctl-tester PASS 4.75 seconds
TestRunner_mesh-tester PASS 10.87 seconds
TestRunner_smp-tester PASS 4.49 seconds
TestRunner_userchan-tester PASS 3.27 seconds
TestRunner_6lowpan-tester PASS 5.38 seconds
IncrementalBuild PASS 28.91 seconds
Details
##############################
Test: CheckPatch - FAIL
Desc: Run checkpatch.pl script
Output:
Bluetooth: delete the new SCO link if linking it fails
WARNING: Non-standard signature: Assisted-by:
#96:
Assisted-by: DeepSeek-V4.1-Flash and OpenAI Codex
ERROR: Unrecognized email address: 'DeepSeek-V4.1-Flash and OpenAI Codex'
#96:
Assisted-by: DeepSeek-V4.1-Flash and OpenAI Codex
total: 1 errors, 1 warnings, 0 checks, 27 lines checked
NOTE: For some of the reported defects, checkpatch may be able to
mechanically convert to the typical style using --fix or --fix-inplace.
/home/runner/work/bluetooth-next/bluetooth-next/src/patch/14942649.patch has style problems, please review.
NOTE: Ignored message types: UNKNOWN_COMMIT_ID
NOTE: If any of the errors are false positives, please report
them to the maintainer, see CHECKPATCH in MAINTAINERS.
##############################
Test: TestRunner_l2cap-tester - FAIL
Desc: Run l2cap-tester with test-runner
Output:
Sanitizer errors:
==38==ERROR: AddressSanitizer: heap-use-after-free on address 0x7befcd8e33d0 at pc 0x55560205ae8e bp 0x7ffefc4748b0 sp 0x7ffefc4748a0
READ of size 4 at 0x7befcd8e33d0 thread T0
#0 0x55560205ae8d in timeout_callback src/shared/timeout-mainloop.c:33
#1 0x55560205bb75 in timeout_callback src/shared/mainloop.c:270
#2 0x55560205caa6 in mainloop_run src/shared/mainloop.c:124
#3 0x55560205f3fa in mainloop_run_with_signal src/shared/mainloop-notify.c:196
#4 0x55560206464b in tester_run src/shared/tester.c:1223
#5 0x555601f8e17d in main tools/l2cap-tester.c:3918
#6 0x7fafce844600 in __libc_start_call_main ../sysdeps/nptl/libc_start_call_main.h:59
#7 0x7fafce844717 in __libc_start_main_impl ../csu/libc-start.c:360
#8 0x555601f94c84 in _start (/home/runner/work/bluetooth-next/bluetooth-next/src/bluez/tools/l2cap-tester+0x16cc84) (BuildId: 91c9d49e9766c394468e27ffa29b05e7d348169f)
0x7befcd8e33d0 is located 0 bytes inside of 40-byte region [0x7befcd8e33d0,0x7befcd8e33f8)
freed by thread T0 here:
#0 0x7fafcf1823ff in free ../../../../src/libsanitizer/asan/asan_malloc_linux.cpp:51
#1 0x55560205b36a in timeout_destroy src/shared/mainloop.c:251
previously allocated by thread T0 here:
#0 0x7fafcf18360f in malloc ../../../../src/libsanitizer/asan/asan_malloc_linux.cpp:67
#1 0x5556020452d5 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/1057
---
Regards,
Linux Bluetooth
prev parent reply other threads:[~2026-11-04 8:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-04 2:28 [PATCH] Bluetooth: delete the new SCO link if linking it fails Wentao Liang
2026-11-04 7:12 ` Krzysztof Kozlowski
2026-11-04 8:46 ` bluez.test.bot [this message]
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=6aeaf0cd.6510e82a.12e6b9.fc61@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=vulab@iscas.ac.cn \
/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.