From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, pav@iki.fi
Subject: RE: Bluetooth: fix hci_conn lookup RCU usage + holding refcounts
Date: Fri, 10 Jul 2026 04:18:11 -0700 (PDT) [thread overview]
Message-ID: <6a50d4f3.d6f58ba8.245457.f39b@mx.google.com> (raw)
In-Reply-To: <4853db33fb044122e1eac76736c5cd0529d13349.1783671570.git.pav@iki.fi>
[-- Attachment #1: Type: text/plain, Size: 2851 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/project/bluetooth/list/?series=1125224
---Test result---
Test Summary:
CheckPatch PASS 2.91 seconds
VerifyFixes PASS 0.13 seconds
VerifySignedoff PASS 0.14 seconds
GitLint FAIL 1.36 seconds
SubjectPrefix PASS 0.51 seconds
BuildKernel PASS 25.35 seconds
CheckAllWarning PASS 28.18 seconds
CheckSparse PASS 27.07 seconds
BuildKernel32 PASS 24.61 seconds
CheckKernelLLVM SKIP 0.00 seconds
TestRunnerSetup PASS 461.28 seconds
TestRunner_l2cap-tester FAIL 62.18 seconds
TestRunner_iso-tester PASS 87.34 seconds
TestRunner_bnep-tester PASS 19.46 seconds
TestRunner_mgmt-tester FAIL 208.74 seconds
TestRunner_rfcomm-tester PASS 25.23 seconds
TestRunner_sco-tester PASS 32.15 seconds
TestRunner_ioctl-tester PASS 25.37 seconds
TestRunner_mesh-tester FAIL 26.07 seconds
TestRunner_smp-tester PASS 22.99 seconds
TestRunner_userchan-tester PASS 21.93 seconds
TestRunner_6lowpan-tester PASS 22.15 seconds
IncrementalBuild PASS 39.87 seconds
Details
##############################
Test: GitLint - FAIL
Desc: Run gitlint
Output:
[v3,2/4] Bluetooth: mgmt: fix locking in unpair_device/disconnect_sync
18: B2 Line has trailing whitespace: " "
##############################
Test: CheckKernelLLVM - SKIP
Desc: Build kernel with LLVM + context analysis
Output:
Clang not found
##############################
Test: TestRunner_l2cap-tester - FAIL
Desc: Run l2cap-tester with test-runner
Output:
Total: 96, Passed: 95 (99.0%), Failed: 1, Not Run: 0
Failed Test Cases
L2CAP BR/EDR Server - Set PHY 1M Failed 0.287 seconds
##############################
Test: TestRunner_mgmt-tester - FAIL
Desc: Run mgmt-tester with test-runner
Output:
Total: 494, Passed: 489 (99.0%), Failed: 1, Not Run: 4
Failed Test Cases
Read Exp Feature - Success Failed 0.234 seconds
##############################
Test: TestRunner_mesh-tester - FAIL
Desc: Run mesh-tester with test-runner
Output:
Total: 10, Passed: 8 (80.0%), Failed: 2, Not Run: 0
Failed Test Cases
Mesh - Send cancel - 1 Timed out 2.786 seconds
Mesh - Send cancel - 2 Timed out 1.990 seconds
https://github.com/bluez/bluetooth-next/pull/420
---
Regards,
Linux Bluetooth
next prev parent reply other threads:[~2026-07-10 11:18 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-10 8:23 [PATCH v3 0/4] Bluetooth: fix hci_conn lookup RCU usage + holding refcounts Pauli Virtanen
2026-07-10 8:23 ` [PATCH v3 1/4] Bluetooth: hci_sync: extend conn_hash lookup critical sections Pauli Virtanen
2026-07-10 11:18 ` bluez.test.bot [this message]
2026-07-10 8:23 ` [PATCH v3 2/4] Bluetooth: mgmt: fix locking in unpair_device/disconnect_sync Pauli Virtanen
2026-07-10 8:23 ` [PATCH v3 3/4] Bluetooth: mgmt: hold reference for hci_conn in mgmt_pending_cmds Pauli Virtanen
2026-07-10 8:23 ` [PATCH v3 4/4] Bluetooth: hci_sync: hold hdev->lock for hci_conn_params lookups Pauli Virtanen
2026-07-10 20:10 ` [PATCH v3 0/4] Bluetooth: fix hci_conn lookup RCU usage + holding refcounts patchwork-bot+bluetooth
-- strict thread matches above, loose matches on Subject: below --
2026-07-05 22:42 [PATCH v2 1/4] Bluetooth: hci_sync: extend conn_hash lookup critical sections Pauli Virtanen
2026-07-05 23:41 ` Bluetooth: fix hci_conn lookup RCU usage + holding refcounts bluez.test.bot
2026-07-05 14:47 [PATCH 1/4] Bluetooth: hci_sync: extend conn_hash lookup RCU critical sections Pauli Virtanen
2026-07-05 15:35 ` Bluetooth: fix hci_conn lookup RCU usage + holding refcounts bluez.test.bot
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=6a50d4f3.d6f58ba8.245457.f39b@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=pav@iki.fi \
/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