From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, jaggyaur@gmail.com
Subject: RE: [v4] Bluetooth: hci_core: Fix UAF in hci_unregister_dev()
Date: Wed, 03 Jun 2026 05:39:19 -0700 (PDT) [thread overview]
Message-ID: <6a202077.50eb26ae.2d7cf3.e8b9@mx.google.com> (raw)
In-Reply-To: <20260603085047.256779-1-jaggyaur@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2472 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=1105168
---Test result---
Test Summary:
CheckPatch PASS 0.72 seconds
VerifyFixes PASS 0.14 seconds
VerifySignedoff PASS 0.13 seconds
GitLint PASS 0.33 seconds
SubjectPrefix PASS 0.13 seconds
BuildKernel PASS 25.12 seconds
CheckAllWarning PASS 27.85 seconds
CheckSparse PASS 26.29 seconds
BuildKernel32 PASS 24.34 seconds
TestRunnerSetup PASS 519.77 seconds
TestRunner_l2cap-tester FAIL 58.96 seconds
TestRunner_iso-tester PASS 75.65 seconds
TestRunner_bnep-tester PASS 19.41 seconds
TestRunner_mgmt-tester FAIL 209.19 seconds
TestRunner_rfcomm-tester PASS 25.68 seconds
TestRunner_sco-tester PASS 32.57 seconds
TestRunner_ioctl-tester PASS 26.29 seconds
TestRunner_mesh-tester FAIL 25.39 seconds
TestRunner_smp-tester PASS 23.55 seconds
TestRunner_userchan-tester PASS 19.76 seconds
TestRunner_6lowpan-tester PASS 22.67 seconds
IncrementalBuild PASS 24.73 seconds
Details
##############################
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 3M Failed 0.251 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.241 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.048 seconds
Mesh - Send cancel - 2 Timed out 1.988 seconds
https://github.com/bluez/bluetooth-next/pull/280
---
Regards,
Linux Bluetooth
next prev parent reply other threads:[~2026-06-03 12:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-03 8:50 [PATCH v4] Bluetooth: hci_core: Fix UAF in hci_unregister_dev() Jordan Walters
2026-06-03 12:39 ` bluez.test.bot [this message]
2026-06-03 17:50 ` 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=6a202077.50eb26ae.2d7cf3.e8b9@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=jaggyaur@gmail.com \
--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