From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, doruk@0sec.ai
Subject: RE: Bluetooth: L2CAP: take chan_l lock in ecred defer recvmsg path to fix list corruption
Date: Tue, 14 Jul 2026 07:49:27 -0700 (PDT) [thread overview]
Message-ID: <6a564c77.b4a331f0.271e68.7822@mx.google.com> (raw)
In-Reply-To: <20260714125209.39790-1-doruk@0sec.ai>
[-- Attachment #1: Type: text/plain, Size: 2267 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=1127425
---Test result---
Test Summary:
CheckPatch FAIL 0.59 seconds
VerifyFixes PASS 0.08 seconds
VerifySignedoff PASS 0.07 seconds
GitLint FAIL 0.21 seconds
SubjectPrefix PASS 0.07 seconds
BuildKernel PASS 26.65 seconds
CheckAllWarning PASS 29.65 seconds
CheckSparse PASS 27.95 seconds
BuildKernel32 PASS 26.37 seconds
CheckKernelLLVM SKIP 0.00 seconds
TestRunnerSetup PASS 505.78 seconds
TestRunner_l2cap-tester PASS 63.67 seconds
IncrementalBuild PASS 26.67 seconds
Details
##############################
Test: CheckPatch - FAIL
Desc: Run checkpatch.pl script
Output:
Bluetooth: L2CAP: take chan_l lock in ecred defer recvmsg path to fix list corruption
WARNING: Assisted-by expects 'AGENT_NAME:MODEL_VERSION [TOOL1] [TOOL2]' format
#139:
Assisted-by: 0sec
total: 0 errors, 1 warnings, 0 checks, 41 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/14686349.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: GitLint - FAIL
Desc: Run gitlint
Output:
Bluetooth: L2CAP: take chan_l lock in ecred defer recvmsg path to fix list corruption
1: T1 Title exceeds max length (85>80): "Bluetooth: L2CAP: take chan_l lock in ecred defer recvmsg path to fix list corruption"
##############################
Test: CheckKernelLLVM - SKIP
Desc: Build kernel with LLVM + context analysis
Output:
Clang not found
https://github.com/bluez/bluetooth-next/pull/438
---
Regards,
Linux Bluetooth
prev parent reply other threads:[~2026-07-14 14:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-14 12:52 [PATCH] Bluetooth: L2CAP: take chan_l lock in ecred defer recvmsg path to fix list corruption Doruk Tan Ozturk
2026-07-14 14:49 ` 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=6a564c77.b4a331f0.271e68.7822@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 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.