From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, sammiee5311@gmail.com
Subject: RE: Bluetooth: eir: Fix OOB read in eir_get_service_data()
Date: Wed, 24 Jun 2026 07:19:56 -0700 (PDT) [thread overview]
Message-ID: <6a3be78c.5c7f968c.45680.b5d5@mx.google.com> (raw)
In-Reply-To: <20260624115439.868817-1-sammiee5311@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2653 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=1115877
---Test result---
Test Summary:
CheckPatch PASS 1.35 seconds
VerifyFixes PASS 0.31 seconds
VerifySignedoff PASS 0.20 seconds
GitLint FAIL 0.71 seconds
SubjectPrefix PASS 0.37 seconds
BuildKernel PASS 27.00 seconds
CheckAllWarning PASS 29.24 seconds
CheckSparse PASS 27.97 seconds
BuildKernel32 PASS 25.97 seconds
CheckKernelLLVM SKIP 0.00 seconds
TestRunnerSetup PASS 574.54 seconds
TestRunner_l2cap-tester PASS 57.98 seconds
TestRunner_iso-tester PASS 78.50 seconds
TestRunner_bnep-tester PASS 18.88 seconds
TestRunner_mgmt-tester FAIL 209.96 seconds
TestRunner_rfcomm-tester PASS 25.44 seconds
TestRunner_sco-tester PASS 32.55 seconds
TestRunner_ioctl-tester PASS 25.60 seconds
TestRunner_mesh-tester FAIL 26.07 seconds
TestRunner_smp-tester PASS 22.95 seconds
TestRunner_userchan-tester PASS 19.95 seconds
TestRunner_6lowpan-tester PASS 22.94 seconds
IncrementalBuild PASS 25.85 seconds
Details
##############################
Test: GitLint - FAIL
Desc: Run gitlint
Output:
Bluetooth: eir: Fix OOB read in eir_get_service_data()
11: B3 Line contains hard tab characters (\t): " eir += dlen;"
12: B3 Line contains hard tab characters (\t): " eir_len -= dlen;"
##############################
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: 494, Passed: 489 (99.0%), Failed: 1, Not Run: 4
Failed Test Cases
Read Exp Feature - Success Failed 0.233 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.439 seconds
Mesh - Send cancel - 2 Timed out 1.991 seconds
https://github.com/bluez/bluetooth-next/pull/347
---
Regards,
Linux Bluetooth
next prev parent reply other threads:[~2026-06-24 14:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-24 11:54 [PATCH] Bluetooth: eir: Fix OOB read in eir_get_service_data() HyeongJun An
2026-06-24 14:19 ` bluez.test.bot [this message]
2026-06-24 14:32 ` [PATCH v2] " HyeongJun An
2026-06-24 16:39 ` [v2] " 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=6a3be78c.5c7f968c.45680.b5d5@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=sammiee5311@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