From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, cochcoder@proton.me
Subject: RE: [1/1] Bluetooth: reject invalid LE supervision timeout relationships
Date: Thu, 05 Nov 2026 19:26:08 -0800 (PST) [thread overview]
Message-ID: <6aed48d0.27a8fa0c.ab8a3.c92a@mx.google.com> (raw)
In-Reply-To: <20261106021809.631456-1-cochcoder@proton.me>
[-- Attachment #1: Type: text/plain, Size: 4023 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/1203685/
---Test result---
Test Summary:
CheckPatch FAIL 2.38 seconds
VerifyFixes PASS 0.13 seconds
VerifySignedoff PASS 4.33 seconds
GitLint PASS 2.87 seconds
SubjectPrefix PASS 0.17 seconds
BuildKernel PASS 42.30 seconds
CheckAllWarning PASS 36.61 seconds
CheckSparse PASS 39.09 seconds
BuildKernel32 PASS 34.96 seconds
CheckKernelLLVM PASS 35.11 seconds
TestRunnerSetup PASS 755.31 seconds
TestRunner_l2cap-tester FAIL 10.73 seconds
TestRunner_iso-tester PASS 11.05 seconds
TestRunner_bnep-tester PASS 3.24 seconds
TestRunner_mgmt-tester PASS 89.13 seconds
TestRunner_rfcomm-tester PASS 4.73 seconds
TestRunner_sco-tester PASS 5.73 seconds
TestRunner_ioctl-tester PASS 4.75 seconds
TestRunner_mesh-tester PASS 5.63 seconds
TestRunner_smp-tester PASS 4.43 seconds
TestRunner_userchan-tester PASS 3.44 seconds
TestRunner_6lowpan-tester PASS 4.90 seconds
IncrementalBuild PASS 29.31 seconds
Details
##############################
Test: CheckPatch - FAIL
Desc: Run checkpatch.pl script
Output:
[1/1] Bluetooth: reject invalid LE supervision timeout relationships
WARNING: Non-standard signature: Assisted-by:
#99:
Assisted-by: LLM
ERROR: Unrecognized email address: 'LLM'
#99:
Assisted-by: LLM
total: 1 errors, 1 warnings, 30 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/14955884.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:
==35==ERROR: AddressSanitizer: heap-use-after-free on address 0x7b7dc18e33d0 at pc 0x560bc1481eee bp 0x7fff2ba55e70 sp 0x7fff2ba55e60
READ of size 4 at 0x7b7dc18e33d0 thread T0
#0 0x560bc1481eed in timeout_callback src/shared/timeout-mainloop.c:33
#1 0x560bc1482ed5 in timeout_callback src/shared/mainloop.c:271
#2 0x560bc1484006 in mainloop_run src/shared/mainloop.c:125
#3 0x560bc148696a in mainloop_run_with_signal src/shared/mainloop-notify.c:196
#4 0x560bc148bc4b in tester_run src/shared/tester.c:1297
#5 0x560bc13b51dd in main tools/l2cap-tester.c:3918
#6 0x7f3dc27ec600 in __libc_start_call_main ../sysdeps/nptl/libc_start_call_main.h:59
#7 0x7f3dc27ec717 in __libc_start_main_impl ../csu/libc-start.c:360
#8 0x560bc13bbce4 in _start (/home/runner/work/bluetooth-next/bluetooth-next/src/bluez/tools/l2cap-tester+0x16dce4) (BuildId: 0d2067a7ef8fe61fcf622598953c7d0f996221a0)
0x7b7dc18e33d0 is located 0 bytes inside of 40-byte region [0x7b7dc18e33d0,0x7b7dc18e33f8)
freed by thread T0 here:
#0 0x7f3dc312a3ff in free ../../../../src/libsanitizer/asan/asan_malloc_linux.cpp:51
#1 0x560bc14823ca in timeout_destroy src/shared/mainloop.c:252
previously allocated by thread T0 here:
#0 0x7f3dc312b60f in malloc ../../../../src/libsanitizer/asan/asan_malloc_linux.cpp:67
#1 0x560bc146c335 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/1076
---
Regards,
Linux Bluetooth
next prev parent reply other threads:[~2026-11-06 3:26 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-13 3:31 [RFC PATCH] Bluetooth: l2cap: honor local LE connection interval range Kyle Pepper
2026-10-13 4:26 ` [RFC] " bluez.test.bot
2026-10-13 14:33 ` [RFC PATCH] " Luiz Augusto von Dentz
2026-10-15 18:12 ` cochcoder
2026-10-15 4:34 ` [RFC PATCH v2] Bluetooth: l2cap: prefer compatible local LE intervals Kyle Pepper
2026-10-15 7:12 ` [RFC,v2] " bluez.test.bot
2026-10-15 18:11 ` [RFC PATCH v3] " Kyle Pepper
2026-10-15 20:17 ` [RFC,v3] " bluez.test.bot
2026-10-31 18:09 ` [RFC PATCH v3] " cochcoder
2026-11-06 2:18 ` [PATCH 1/1] Bluetooth: reject invalid LE supervision timeout relationships Kyle Pepper
2026-11-06 3:26 ` bluez.test.bot [this message]
2026-11-06 4:28 ` cochcoder
2026-11-06 16:28 ` Luiz Augusto von Dentz
2026-11-06 17:24 ` [PATCH v2 " Kyle Pepper
2026-11-06 20:20 ` 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=6aed48d0.27a8fa0c.ab8a3.c92a@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=cochcoder@proton.me \
--cc=linux-bluetooth@vger.kernel.org \
/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