From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, kbreddy.rpbc@gmail.com
Subject: RE: [v4] Bluetooth: fix memory leak in error path of hci_alloc_dev()
Date: Sun, 31 May 2026 12:32:12 -0700 (PDT) [thread overview]
Message-ID: <6a1c8cbc.8d510ab8.182f74.9adf@mx.google.com> (raw)
In-Reply-To: <20260531185339.107188-1-kbreddy.rpbc@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2659 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=1103659
---Test result---
Test Summary:
CheckPatch PASS 0.75 seconds
VerifyFixes PASS 0.14 seconds
VerifySignedoff PASS 0.14 seconds
GitLint FAIL 0.34 seconds
SubjectPrefix PASS 0.14 seconds
BuildKernel PASS 24.71 seconds
CheckAllWarning PASS 27.34 seconds
CheckSparse PASS 26.77 seconds
BuildKernel32 PASS 24.39 seconds
TestRunnerSetup PASS 521.61 seconds
TestRunner_l2cap-tester PASS 58.27 seconds
TestRunner_iso-tester PASS 71.09 seconds
TestRunner_bnep-tester PASS 19.01 seconds
TestRunner_mgmt-tester FAIL 210.04 seconds
TestRunner_rfcomm-tester PASS 25.47 seconds
TestRunner_sco-tester PASS 32.52 seconds
TestRunner_ioctl-tester PASS 25.65 seconds
TestRunner_mesh-tester FAIL 25.96 seconds
TestRunner_smp-tester PASS 23.39 seconds
TestRunner_userchan-tester PASS 19.79 seconds
TestRunner_6lowpan-tester PASS 22.57 seconds
IncrementalBuild PASS 23.69 seconds
Details
##############################
Test: GitLint - FAIL
Desc: Run gitlint
Output:
[v4] Bluetooth: fix memory leak in error path of hci_alloc_dev()
27: B2 Line has trailing whitespace: " - Added missing curly braces to the if/else block in bt_host_release() "
32: B2 Line has trailing whitespace: " - Fixed a NULL pointer dereference caused by v1. "
33: B2 Line has trailing whitespace: " - Moved cleanup_srcu_struct() to the fallback (unregistered) branch "
##############################
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.246 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.303 seconds
Mesh - Send cancel - 2 Timed out 1.995 seconds
https://github.com/bluez/bluetooth-next/pull/261
---
Regards,
Linux Bluetooth
prev parent reply other threads:[~2026-05-31 19:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-31 18:53 [PATCH v4] Bluetooth: fix memory leak in error path of hci_alloc_dev() Bharath Reddy
2026-05-31 19:32 ` bluez.test.bot [this message]
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=6a1c8cbc.8d510ab8.182f74.9adf@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=kbreddy.rpbc@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