From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, zzzccc427@gmail.com
Subject: RE: Bluetooth: Keep borrowed keys inside RCU sections
Date: Thu, 29 Oct 2026 07:50:56 -0700 (PDT) [thread overview]
Message-ID: <6ae35d50.ba263b4e.364d69.34b0@mx.google.com> (raw)
In-Reply-To: <pm-bluetooth-objects-candidate-0122-v8-952ad9eb0ef59367ba6a-1@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 6288 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/1196273/
---Test result---
Test Summary:
CheckPatch FAIL 5.59 seconds
VerifyFixes PASS 0.13 seconds
VerifySignedoff PASS 0.13 seconds
GitLint FAIL 1.37 seconds
SubjectPrefix PASS 0.48 seconds
BuildKernel PASS 32.31 seconds
CheckAllWarning PASS 36.86 seconds
CheckSparse PASS 40.06 seconds
BuildKernel32 PASS 32.70 seconds
CheckKernelLLVM PASS 37.40 seconds
TestRunnerSetup PASS 759.22 seconds
TestRunner_l2cap-tester PASS 12.84 seconds
TestRunner_iso-tester PASS 13.00 seconds
TestRunner_bnep-tester PASS 3.22 seconds
TestRunner_mgmt-tester PASS 88.44 seconds
TestRunner_rfcomm-tester PASS 4.58 seconds
TestRunner_sco-tester PASS 5.73 seconds
TestRunner_ioctl-tester PASS 4.74 seconds
TestRunner_mesh-tester PASS 5.61 seconds
TestRunner_smp-tester PASS 4.43 seconds
TestRunner_userchan-tester PASS 3.28 seconds
TestRunner_6lowpan-tester PASS 4.47 seconds
IncrementalBuild PASS 40.49 seconds
Details
##############################
Test: CheckPatch - FAIL
Desc: Run checkpatch.pl script
Output:
[1/4] Bluetooth: hci_core: Keep link-key filtering inside RCU
WARNING: Prefer a maximum 75 chars per line (possible unwrapped commit description?)
#289:
page: refcount:0 mapcount:0 mapping:0000000000000000 index:0x0 pfn:0x10b5f8
total: 0 errors, 1 warnings, 0 checks, 19 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/14924412.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/4] Bluetooth: SMP: Protect link keys during LTK derivation
WARNING: Prefer a maximum 75 chars per line (possible unwrapped commit description?)
#272:
page: refcount:0 mapcount:0 mapping:0000000000000000 index:0x0 pfn:0x10618e
total: 0 errors, 1 warnings, 0 checks, 36 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/14924414.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.
[3/4] Bluetooth: SMP: Protect LTK encryption with RCU
WARNING: Prefer a maximum 75 chars per line (possible unwrapped commit description?)
#171:
kfence-#128: 0x00000000d45af9b0-0x0000000053c1365e, size=72, cache=kmalloc-96
total: 0 errors, 1 warnings, 0 checks, 33 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/14924413.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.
[4/4] Bluetooth: hci_sync: Copy the resolving-list IRK under RCU
WARNING: Prefer a maximum 75 chars per line (possible unwrapped commit description?)
#248:
page: refcount:0 mapcount:0 mapping:0000000000000000 index:0x0 pfn:0x10d214
total: 0 errors, 1 warnings, 0 checks, 25 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/14924415.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/4] Bluetooth: hci_core: Keep link-key filtering inside RCU
44: B1 Line exceeds max length (107>80): " CPU: 1 UID: 0 PID: 502 Comm: kworker/u17:0 Not tainted 7.2.0-rc6-pmb-bt-functional-v1+ #5 PREEMPT(lazy)"
45: 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"
[2/4] Bluetooth: SMP: Protect link keys during LTK derivation
39: B1 Line exceeds max length (107>80): " CPU: 0 UID: 0 PID: 500 Comm: kworker/u17:0 Not tainted 7.2.0-rc6-pmb-bt-functional-v1+ #1 PREEMPT(lazy)"
40: 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"
[3/4] Bluetooth: SMP: Protect LTK encryption with RCU
48: B1 Line exceeds max length (81>80): " kfence-#128: 0x00000000d45af9b0-0x0000000053c1365e, size=72, cache=kmalloc-96"
80: B1 Line exceeds max length (109>80): " CPU: 2 UID: 0 PID: 534 Comm: l2cap-ltk-actor Not tainted 7.2.0-rc6-pmb-bt-functional-v1+ #5 PREEMPT(lazy)"
81: 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"
[4/4] Bluetooth: hci_sync: Copy the resolving-list IRK under RCU
41: B1 Line exceeds max length (107>80): " CPU: 2 UID: 0 PID: 504 Comm: kworker/u17:0 Not tainted 7.2.0-rc6-pmb-bt-functional-v1+ #2 PREEMPT(lazy)"
42: 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"
https://github.com/bluez/bluetooth-next/pull/1023
---
Regards,
Linux Bluetooth
next prev parent reply other threads:[~2026-10-29 14:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-29 13:12 [PATCH 0/4] Bluetooth: Keep borrowed keys inside RCU sections Cen Zhang
2026-10-29 13:12 ` [PATCH 1/4] Bluetooth: hci_core: Keep link-key filtering inside RCU Cen Zhang
2026-10-29 14:50 ` bluez.test.bot [this message]
2026-10-29 13:12 ` [PATCH 2/4] Bluetooth: SMP: Protect link keys during LTK derivation Cen Zhang
2026-10-29 13:12 ` [PATCH 3/4] Bluetooth: SMP: Protect LTK encryption with RCU Cen Zhang
2026-10-29 13:12 ` [PATCH 4/4] Bluetooth: hci_sync: Copy the resolving-list IRK under RCU 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=6ae35d50.ba263b4e.364d69.34b0@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