From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, jannh@google.com
Subject: RE: Bluetooth: fix UAF read of ->accept_q in bt_accept_poll()
Date: Mon, 04 May 2026 08:51:10 -0700 (PDT) [thread overview]
Message-ID: <69f8c06e.050a0220.14571e.7585@mx.google.com> (raw)
In-Reply-To: <20260504-bluetooth-accept-uaf-fix-v1-1-1ca63c0efadd@google.com>
[-- Attachment #1: Type: text/plain, Size: 3639 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=1089360
---Test result---
Test Summary:
CheckPatch PASS 0.63 seconds
GitLint FAIL 0.21 seconds
SubjectPrefix PASS 0.06 seconds
BuildKernel PASS 26.94 seconds
CheckAllWarning PASS 29.43 seconds
CheckSparse PASS 28.45 seconds
BuildKernel32 PASS 26.62 seconds
TestRunnerSetup PASS 554.33 seconds
TestRunner_l2cap-tester FAIL 6.36 seconds
TestRunner_iso-tester PASS 294.03 seconds
TestRunner_bnep-tester FAIL 6.60 seconds
TestRunner_mgmt-tester FAIL 8.86 seconds
TestRunner_rfcomm-tester PASS 28.81 seconds
TestRunner_sco-tester PASS 67.96 seconds
TestRunner_ioctl-tester FAIL 37.29 seconds
TestRunner_mesh-tester PASS 27.03 seconds
TestRunner_smp-tester PASS 6.53 seconds
TestRunner_userchan-tester FAIL 6.70 seconds
TestRunner_6lowpan-tester PASS 22.87 seconds
IncrementalBuild PASS 24.55 seconds
Details
##############################
Test: GitLint - FAIL
Desc: Run gitlint
Output:
Bluetooth: fix UAF read of ->accept_q in bt_accept_poll()
WARNING: I3 - ignore-body-lines: gitlint will be switching from using Python regex 'match' (match beginning) to 'search' (match anywhere) semantics. Please review your ignore-body-lines.regex option accordingly. To remove this warning, set general.regex-style-search=True. More details: https://jorisroovers.github.io/gitlint/configuration/#regex-style-search
61: B2 Line has trailing whitespace: "-- "
##############################
Test: TestRunner_l2cap-tester - FAIL
Desc: Run l2cap-tester with test-runner
Output:
No test result found
##############################
Test: TestRunner_bnep-tester - FAIL
Desc: Run bnep-tester with test-runner
Output:
No test result found
##############################
Test: TestRunner_mgmt-tester - FAIL
Desc: Run mgmt-tester with test-runner
Output:
No test result found
##############################
Test: TestRunner_ioctl-tester - FAIL
Desc: Run ioctl-tester with test-runner
Output:
Total: 28, Passed: 0 (0.0%), Failed: 11, Not Run: 17
Failed Test Cases
Device List Timed out -30.834 seconds
Device Info Timed out -6.182 seconds
Reset Stat Timed out -6.185 seconds
Set Link Mode - ACCEPT Timed out -6.188 seconds
Set Pkt Type - DM Timed out -14.375 seconds
Set Pkt Type - DH Timed out -14.378 seconds
Set Pkt Type - HV Timed out -14.380 seconds
Set Pkt Type - 2-DH Timed out -14.383 seconds
Set Pkt Type - 2-DH Timed out -14.386 seconds
Set Pkt Type - ALL Timed out -14.388 seconds
Set ACL MTU - 1 Timed out -14.391 seconds
##############################
Test: TestRunner_userchan-tester - FAIL
Desc: Run userchan-tester with test-runner
Output:
No test result found
https://github.com/bluez/bluetooth-next/pull/143
---
Regards,
Linux Bluetooth
next prev parent reply other threads:[~2026-05-04 15:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-04 15:10 [PATCH] Bluetooth: fix UAF read of ->accept_q in bt_accept_poll() Jann Horn
2026-05-04 15:51 ` bluez.test.bot [this message]
2026-05-05 15:06 ` Luiz Augusto von Dentz
2026-05-06 12:04 ` Jann Horn
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=69f8c06e.050a0220.14571e.7585@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=jannh@google.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