From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, ngocthang2710.1999@gmail.com
Subject: RE: [v2] Bluetooth: af_bluetooth: Fix double list_del and UAF in accept_q
Date: Fri, 18 Sep 2026 03:36:36 -0700 (PDT) [thread overview]
Message-ID: <6aad1434.98a076dd.1114ed.2810@mx.google.com> (raw)
In-Reply-To: <20260918075535.886816-1-ngocthang2710.1999@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2525 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/series/1168407/
---Test result---
Test Summary:
CheckPatch PASS 0.46 seconds
VerifyFixes PASS 0.06 seconds
VerifySignedoff PASS 0.06 seconds
GitLint FAIL 0.18 seconds
SubjectPrefix PASS 0.05 seconds
BuildKernel PASS 21.71 seconds
CheckAllWarning PASS 25.22 seconds
CheckSparse PASS 28.62 seconds
BuildKernel32 PASS 27.86 seconds
CheckKernelLLVM PASS 25.40 seconds
TestRunnerSetup PASS 571.80 seconds
TestRunner_l2cap-tester PASS 17.28 seconds
TestRunner_iso-tester PASS 25.42 seconds
TestRunner_bnep-tester PASS 2.77 seconds
TestRunner_mgmt-tester FAIL 56.51 seconds
TestRunner_rfcomm-tester PASS 4.01 seconds
TestRunner_sco-tester PASS 7.07 seconds
TestRunner_ioctl-tester PASS 4.15 seconds
TestRunner_mesh-tester FAIL 7.63 seconds
TestRunner_smp-tester PASS 3.93 seconds
TestRunner_userchan-tester PASS 2.83 seconds
TestRunner_6lowpan-tester PASS 3.94 seconds
IncrementalBuild PASS 21.75 seconds
Details
##############################
Test: GitLint - FAIL
Desc: Run gitlint
Output:
[v2] Bluetooth: af_bluetooth: Fix double list_del and UAF in accept_q
28: B1 Line exceeds max length (106>80): " - Move sock_put() outside of the spinlock to avoid sleeping in atomic context (suggested by Paavo Helde)."
##############################
Test: TestRunner_mgmt-tester - FAIL
Desc: Run mgmt-tester with test-runner
Output:
Total: 501, Passed: 496 (99.0%), Failed: 1, Not Run: 4
Failed Test Cases
Read Exp Feature - Success Failed 0.015 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.525 seconds
Mesh - Send cancel - 2 Timed out 2.000 seconds
https://github.com/bluez/bluetooth-next/pull/787
---
Regards,
Linux Bluetooth
prev parent reply other threads:[~2026-09-18 10:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-18 7:55 [PATCH v2] Bluetooth: af_bluetooth: Fix double list_del and UAF in accept_q Nguyen Ngoc Thang
2026-09-18 10:36 ` 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=6aad1434.98a076dd.1114ed.2810@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=ngocthang2710.1999@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 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.