From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, doruk@0sec.ai
Subject: RE: [v2] Bluetooth: hci_sync: fix UAF in hci_le_create_cis_sync
Date: Tue, 26 May 2026 14:55:29 -0700 (PDT) [thread overview]
Message-ID: <6a1616d1.d5797644.332336.a18b@mx.google.com> (raw)
In-Reply-To: <20260526194816.65669-1-doruk@0sec.ai>
[-- Attachment #1: Type: text/plain, Size: 3353 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=1101233
---Test result---
Test Summary:
CheckPatch FAIL 0.57 seconds
VerifyFixes PASS 0.08 seconds
VerifySignedoff PASS 0.07 seconds
GitLint PASS 0.50 seconds
SubjectPrefix PASS 0.07 seconds
BuildKernel PASS 27.63 seconds
CheckAllWarning PASS 29.79 seconds
CheckSparse PASS 27.65 seconds
BuildKernel32 PASS 25.96 seconds
TestRunnerSetup PASS 576.60 seconds
TestRunner_l2cap-tester PASS 60.69 seconds
TestRunner_iso-tester PASS 82.77 seconds
TestRunner_bnep-tester PASS 20.17 seconds
TestRunner_mgmt-tester FAIL 225.21 seconds
TestRunner_rfcomm-tester PASS 26.55 seconds
TestRunner_sco-tester PASS 33.64 seconds
TestRunner_ioctl-tester PASS 26.47 seconds
TestRunner_mesh-tester FAIL 25.88 seconds
TestRunner_smp-tester PASS 23.88 seconds
TestRunner_userchan-tester PASS 20.88 seconds
TestRunner_6lowpan-tester PASS 23.41 seconds
IncrementalBuild FAIL 4.17 seconds
Details
##############################
Test: CheckPatch - FAIL
Desc: Run checkpatch.pl script
Output:
[v2] Bluetooth: hci_sync: fix UAF in hci_le_create_cis_sync
ERROR: Please use git commit description style 'commit <12+ chars of sha1> ("<title line>")' - ie: 'commit 035c25007c9e ("Bluetooth: hci_sync: Fix UAF in le_read_features_complete")'
#121:
This is the same class of bug as the one fixed by commit
total: 1 errors, 0 warnings, 0 checks, 22 lines checked
NOTE: For some of the reported defects, checkpatch may be able to
mechanically convert to the typical style using --fix or --fix-inplace.
/github/workspace/src/patch/14596093.patch has style problems, please review.
NOTE: Ignored message types: UNKNOWN_COMMIT_ID
NOTE: If any of the errors are false positives, please report
them to the maintainer, see CHECKPATCH in MAINTAINERS.
##############################
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.271 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.993 seconds
Mesh - Send cancel - 2 Timed out 1.989 seconds
##############################
Test: IncrementalBuild - FAIL
Desc: Incremental build with the patches in the series
Output:
error: patch failed: net/bluetooth/hci_sync.c:6700
error: net/bluetooth/hci_sync.c: patch does not apply
hint: Use 'git am --show-current-patch' to see the failed patch
https://github.com/bluez/bluetooth-next/pull/247
---
Regards,
Linux Bluetooth
prev parent reply other threads:[~2026-05-26 21:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-26 19:48 [PATCH v2] Bluetooth: hci_sync: fix UAF in hci_le_create_cis_sync Doruk Tan Ozturk
2026-05-26 21:55 ` 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=6a1616d1.d5797644.332336.a18b@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=doruk@0sec.ai \
--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