From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, zzzccc427@gmail.com
Subject: RE: Bluetooth: SMP: Serialize root channel updates
Date: Fri, 30 Oct 2026 09:41:19 -0700 (PDT) [thread overview]
Message-ID: <6ae4c8af.f81d2e1b.37c053.3bd7@mx.google.com> (raw)
In-Reply-To: <pm-bluetooth-objects-candidate-0184-v7-c26e53b52c260063ab6a-1@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 7090 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/1197223/
---Test result---
Test Summary:
CheckPatch FAIL 1.92 seconds
VerifyFixes PASS 0.10 seconds
VerifySignedoff PASS 0.10 seconds
GitLint FAIL 0.57 seconds
SubjectPrefix PASS 0.19 seconds
BuildKernel PASS 26.32 seconds
CheckAllWarning PASS 29.35 seconds
CheckSparse PASS 30.87 seconds
BuildKernel32 PASS 26.63 seconds
CheckKernelLLVM PASS 26.68 seconds
TestRunnerSetup PASS 604.48 seconds
TestRunner_l2cap-tester FAIL 12.24 seconds
TestRunner_iso-tester PASS 9.92 seconds
TestRunner_bnep-tester PASS 2.91 seconds
TestRunner_mgmt-tester PASS 85.26 seconds
TestRunner_rfcomm-tester PASS 4.15 seconds
TestRunner_sco-tester PASS 5.23 seconds
TestRunner_ioctl-tester PASS 4.34 seconds
TestRunner_mesh-tester PASS 6.72 seconds
TestRunner_smp-tester PASS 4.26 seconds
TestRunner_userchan-tester PASS 2.92 seconds
TestRunner_6lowpan-tester PASS 4.14 seconds
IncrementalBuild PASS 26.88 seconds
Details
##############################
Test: CheckPatch - FAIL
Desc: Run checkpatch.pl script
Output:
[1/2] Bluetooth: SMP: Serialize forced BR/EDR channel changes
WARNING: Prefer a maximum 75 chars per line (possible unwrapped commit description?)
#176:
Oops: general protection fault, probably for non-canonical address 0xdffffc0000000001: 0000 [#1] SMP KASAN NOPTI
total: 0 errors, 1 warnings, 0 checks, 26 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/14927653.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.
[2/2] Bluetooth: SMP: Serialize root channel replacement
WARNING: Prefer a maximum 75 chars per line (possible unwrapped commit description?)
#281:
page: refcount:0 mapcount:0 mapping:0000000000000000 index:0x0 pfn:0x10c358
total: 0 errors, 1 warnings, 0 checks, 48 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/14927654.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: GitLint - FAIL
Desc: Run gitlint
Output:
[1/2] Bluetooth: SMP: Serialize forced BR/EDR channel changes
53: B1 Line exceeds max length (116>80): " Oops: general protection fault, probably for non-canonical address 0xdffffc0000000001: 0000 [#1] SMP KASAN NOPTI"
55: B1 Line exceeds max length (107>80): " CPU: 1 UID: 0 PID: 497 Comm: kworker/u17:0 Not tainted 7.2.0-rc6-pmb-bt-functional-v1+ #1 PREEMPT(lazy)"
56: B1 Line exceeds max length (119>80): " Hardware name: QEMU Ubuntu 24.04 PC v2 (i440FX + PIIX, arch_caps fix, 1996), BIOS 1.16.3-debian-1.16.3-2 04/01/2014"
59: B1 Line exceeds max length (203>80): " Code: c1 ea 03 80 3c 02 00 0f 85 70 01 00 00 4c 8b a5 a8 04 00 00 48 b8 00 00 00 00 00 fc ff df 49 8d 7c 24 08 48 89 fa 48 c1 ea 03 <80> 3c 02 00 0f 85 6d 01 00 00 4d 8b 64 24 08 4d 85 e4 74 19 e8 2b"
119: B1 Line exceeds max length (96>80): " CPU: 1 UID: 0 PID: 493 Comm: sh Not tainted 7.2.0-rc6-pmb-bt-functional-v1+ #2 PREEMPT(lazy)"
120: B1 Line exceeds max length (119>80): " Hardware name: QEMU Ubuntu 24.04 PC v2 (i440FX + PIIX, arch_caps fix, 1996), BIOS 1.16.3-debian-1.16.3-2 04/01/2014"
147: B1 Line exceeds max length (203>80): " Code: 48 89 fa 4c 89 df e8 58 b3 00 00 8b 93 08 03 00 00 59 5e 48 83 f8 fc 74 1a 5b c3 0f 1f 84 00 00 00 00 00 48 8b 44 24 10 0f 05 <5b> c3 0f 1f 80 00 00 00 00 83 e2 39 83 fa 08 75 de e8 23 ff ff ff"
[2/2] Bluetooth: SMP: Serialize root channel replacement
59: B1 Line exceeds max length (125>80): " CPU: 0 UID: 0 PID: 520 Comm: kworker/u17:0 Tainted: G W 7.2.0-rc6-pmb-bt-functional-v1+ #6 PREEMPT(lazy)"
61: B1 Line exceeds max length (119>80): " Hardware name: QEMU Ubuntu 24.04 PC v2 (i440FX + PIIX, arch_caps fix, 1996), BIOS 1.16.3-debian-1.16.3-2 04/01/2014"
185: B1 Line exceeds max length (125>80): " CPU: 0 UID: 0 PID: 500 Comm: kworker/u17:2 Tainted: G W 7.2.0-rc6-pmb-bt-functional-v1+ #2 PREEMPT(lazy)"
187: B1 Line exceeds max length (119>80): " Hardware name: QEMU Ubuntu 24.04 PC v2 (i440FX + PIIX, arch_caps fix, 1996), BIOS 1.16.3-debian-1.16.3-2 04/01/2014"
299: B1 Line exceeds max length (94>80): " page: refcount:0 mapcount:0 mapping:0000000000000000 index:0xffff8881071f4e00 pfn:0x1071f4"
##############################
Test: TestRunner_l2cap-tester - FAIL
Desc: Run l2cap-tester with test-runner
Output:
Sanitizer errors:
==35==ERROR: AddressSanitizer: heap-use-after-free on address 0x7c24aa8e33d0 at pc 0x55dc41eebe8e bp 0x7ffd90feee80 sp 0x7ffd90feee70
READ of size 4 at 0x7c24aa8e33d0 thread T0
#0 0x55dc41eebe8d in timeout_callback src/shared/timeout-mainloop.c:33
#1 0x55dc41eecb75 in timeout_callback src/shared/mainloop.c:270
#2 0x55dc41eedaa6 in mainloop_run src/shared/mainloop.c:124
#3 0x55dc41ef03fa in mainloop_run_with_signal src/shared/mainloop-notify.c:196
#4 0x55dc41ef564b in tester_run src/shared/tester.c:1223
#5 0x55dc41e1f17d in main tools/l2cap-tester.c:3918
#6 0x7fe4ab80d600 in __libc_start_call_main ../sysdeps/nptl/libc_start_call_main.h:59
#7 0x7fe4ab80d717 in __libc_start_main_impl ../csu/libc-start.c:360
#8 0x55dc41e25c84 in _start (/home/runner/work/bluetooth-next/bluetooth-next/src/bluez/tools/l2cap-tester+0x16cc84) (BuildId: 91c9d49e9766c394468e27ffa29b05e7d348169f)
0x7c24aa8e33d0 is located 0 bytes inside of 40-byte region [0x7c24aa8e33d0,0x7c24aa8e33f8)
freed by thread T0 here:
#0 0x7fe4ac14b3ff in free ../../../../src/libsanitizer/asan/asan_malloc_linux.cpp:51
#1 0x55dc41eec36a in timeout_destroy src/shared/mainloop.c:251
previously allocated by thread T0 here:
#0 0x7fe4ac14c60f in malloc ../../../../src/libsanitizer/asan/asan_malloc_linux.cpp:67
#1 0x55dc41ed62d5 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/1033
---
Regards,
Linux Bluetooth
next prev parent reply other threads:[~2026-10-30 16:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-30 14:43 [PATCH 0/2] Bluetooth: SMP: Serialize root channel updates Cen Zhang
2026-10-30 14:43 ` [PATCH 1/2] Bluetooth: SMP: Serialize forced BR/EDR channel changes Cen Zhang
2026-10-30 16:41 ` bluez.test.bot [this message]
2026-10-30 14:43 ` [PATCH 2/2] Bluetooth: SMP: Serialize root channel replacement 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=6ae4c8af.f81d2e1b.37c053.3bd7@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