From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, acharyalaxman8848@gmail.com
Subject: RE: Bluetooth: hci_event: fix out-of-bounds read in LE PA report reassembly
Date: Wed, 05 Aug 2026 12:41:01 -0700 (PDT) [thread overview]
Message-ID: <6a7391cd.5cacff2a.2ca7ce.1146@mx.google.com> (raw)
In-Reply-To: <20260805173701.6649-1-acharyalaxman8848@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 3442 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=1140947
---Test result---
Test Summary:
CheckPatch PASS 0.76 seconds
VerifyFixes PASS 0.14 seconds
VerifySignedoff PASS 0.14 seconds
GitLint FAIL 0.34 seconds
SubjectPrefix PASS 0.13 seconds
BuildKernel PASS 27.41 seconds
CheckAllWarning PASS 30.00 seconds
CheckSparse PASS 28.64 seconds
BuildKernel32 PASS 26.48 seconds
CheckKernelLLVM SKIP 0.00 seconds
TestRunnerSetup PASS 500.72 seconds
TestRunner_l2cap-tester PASS 63.12 seconds
TestRunner_iso-tester PASS 82.78 seconds
TestRunner_bnep-tester PASS 19.41 seconds
TestRunner_mgmt-tester FAIL 226.06 seconds
TestRunner_rfcomm-tester PASS 25.61 seconds
TestRunner_sco-tester PASS 32.32 seconds
TestRunner_ioctl-tester PASS 26.98 seconds
TestRunner_mesh-tester FAIL 26.08 seconds
TestRunner_smp-tester PASS 24.08 seconds
TestRunner_userchan-tester PASS 20.45 seconds
TestRunner_6lowpan-tester PASS 23.48 seconds
IncrementalBuild PASS 25.91 seconds
Details
##############################
Test: GitLint - FAIL
Desc: Run gitlint
Output:
Bluetooth: hci_event: fix out-of-bounds read in LE PA report reassembly
7: B3 Line contains hard tab characters (\t): " struct hci_ev_le_per_adv_report {"
8: B3 Line contains hard tab characters (\t): " __le16 sync_handle;"
9: B3 Line contains hard tab characters (\t): " __u8 tx_power;"
10: B3 Line contains hard tab characters (\t): " __u8 rssi;"
11: B3 Line contains hard tab characters (\t): " __u8 cte_type;"
12: B3 Line contains hard tab characters (\t): " __u8 data_status;"
13: B3 Line contains hard tab characters (\t): " __u8 length;"
14: B3 Line contains hard tab characters (\t): " __u8 data[];"
15: B3 Line contains hard tab characters (\t): " } __packed;"
22: B3 Line contains hard tab characters (\t): " memcpy(hcon->le_per_adv_data + hcon->le_per_adv_data_offset,"
23: B3 Line contains hard tab characters (\t): " ev->data, ev->length);"
##############################
Test: CheckKernelLLVM - SKIP
Desc: Build kernel with LLVM + context analysis
Output:
Clang not found
##############################
Test: TestRunner_mgmt-tester - FAIL
Desc: Run mgmt-tester with test-runner
Output:
Total: 501, Passed: 495 (98.8%), Failed: 2, Not Run: 4
Failed Test Cases
Read Exp Feature - Success Failed 0.258 seconds
LL Privacy - Unpair 1 Timed out 1.875 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 1.927 seconds
Mesh - Send cancel - 2 Timed out 1.989 seconds
https://github.com/bluez/bluetooth-next/pull/537
---
Regards,
Linux Bluetooth
next prev parent reply other threads:[~2026-08-05 19:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-05 17:37 [PATCH] Bluetooth: hci_event: fix out-of-bounds read in LE PA report reassembly Laxman Acharya
2026-08-05 19:41 ` bluez.test.bot [this message]
2026-08-07 16:30 ` 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=6a7391cd.5cacff2a.2ca7ce.1146@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=acharyalaxman8848@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.