From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, radek@podgorny.cz
Subject: RE: [v2] Bluetooth: find an RPA peer's connection parameters by its identity
Date: Wed, 04 Nov 2026 08:38:06 -0800 (PST) [thread overview]
Message-ID: <6aeb5f6e.e782ec0c.2b3981.c107@mx.google.com> (raw)
In-Reply-To: <20261104120138.1165715-1-radek@podgorny.cz>
[-- Attachment #1: Type: text/plain, Size: 4096 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/1201734/
---Test result---
Test Summary:
CheckPatch FAIL 2.03 seconds
VerifyFixes PASS 10.78 seconds
VerifySignedoff PASS 0.87 seconds
GitLint PASS 0.37 seconds
SubjectPrefix PASS 0.10 seconds
BuildKernel PASS 21.93 seconds
CheckAllWarning PASS 24.10 seconds
CheckSparse PASS 39.62 seconds
BuildKernel32 PASS 26.36 seconds
CheckKernelLLVM PASS 21.52 seconds
TestRunnerSetup PASS 480.51 seconds
TestRunner_l2cap-tester FAIL 11.88 seconds
TestRunner_iso-tester PASS 13.53 seconds
TestRunner_bnep-tester PASS 2.97 seconds
TestRunner_mgmt-tester PASS 83.68 seconds
TestRunner_rfcomm-tester PASS 4.10 seconds
TestRunner_sco-tester PASS 5.26 seconds
TestRunner_ioctl-tester PASS 9.60 seconds
TestRunner_mesh-tester PASS 12.86 seconds
TestRunner_smp-tester PASS 7.67 seconds
TestRunner_userchan-tester PASS 4.06 seconds
TestRunner_6lowpan-tester PASS 4.51 seconds
IncrementalBuild PASS 20.54 seconds
Details
##############################
Test: CheckPatch - FAIL
Desc: Run checkpatch.pl script
Output:
[v2] Bluetooth: find an RPA peer's connection parameters by its identity
WARNING: Non-standard signature: Assisted-by:
#82:
Assisted-by: Claude:claude-opus-5-5
ERROR: Unrecognized email address: 'Claude:claude-opus-5-5'
#82:
Assisted-by: Claude:claude-opus-5-5
total: 1 errors, 1 warnings, 0 checks, 38 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/14943961.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:
==37==ERROR: AddressSanitizer: heap-use-after-free on address 0x7c0d93ce33d0 at pc 0x564f5dac9e8e bp 0x7ffe8f53d490 sp 0x7ffe8f53d480
READ of size 4 at 0x7c0d93ce33d0 thread T0
#0 0x564f5dac9e8d in timeout_callback src/shared/timeout-mainloop.c:33
#1 0x564f5dacab75 in timeout_callback src/shared/mainloop.c:270
#2 0x564f5dacbaa6 in mainloop_run src/shared/mainloop.c:124
#3 0x564f5dace3fa in mainloop_run_with_signal src/shared/mainloop-notify.c:196
#4 0x564f5dad364b in tester_run src/shared/tester.c:1223
#5 0x564f5d9fd17d in main tools/l2cap-tester.c:3918
#6 0x7fcd94c80600 in __libc_start_call_main ../sysdeps/nptl/libc_start_call_main.h:59
#7 0x7fcd94c80717 in __libc_start_main_impl ../csu/libc-start.c:360
#8 0x564f5da03c84 in _start (/home/runner/work/bluetooth-next/bluetooth-next/src/bluez/tools/l2cap-tester+0x16cc84) (BuildId: 91c9d49e9766c394468e27ffa29b05e7d348169f)
0x7c0d93ce33d0 is located 0 bytes inside of 40-byte region [0x7c0d93ce33d0,0x7c0d93ce33f8)
freed by thread T0 here:
#0 0x7fcd955be3ff in free ../../../../src/libsanitizer/asan/asan_malloc_linux.cpp:51
#1 0x564f5daca36a in timeout_destroy src/shared/mainloop.c:251
previously allocated by thread T0 here:
#0 0x7fcd955bf60f in malloc ../../../../src/libsanitizer/asan/asan_malloc_linux.cpp:67
#1 0x564f5dab42d5 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/1063
---
Regards,
Linux Bluetooth
prev parent reply other threads:[~2026-11-04 16:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-04 12:01 [PATCH v2] Bluetooth: find an RPA peer's connection parameters by its identity Radek Podgorny
2026-11-04 14:51 ` Luiz Augusto von Dentz
2026-11-04 16:38 ` 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=6aeb5f6e.e782ec0c.2b3981.c107@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=radek@podgorny.cz \
/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