From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, pav@iki.fi
Subject: RE: Bluetooth: L2CAP: access chan->conn safely in get/setsockopt
Date: Sun, 09 Aug 2026 11:40:43 -0700 (PDT) [thread overview]
Message-ID: <6a78c9ab.d6f58ba8.2929e3.eea1@mx.google.com> (raw)
In-Reply-To: <e4b6658ac62a0dd6ca90e7c7a3d4f58b04ec4b48.1786296912.git.pav@iki.fi>
[-- Attachment #1: Type: text/plain, Size: 2308 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=1142960
---Test result---
Test Summary:
CheckPatch FAIL 1.45 seconds
VerifyFixes PASS 0.13 seconds
VerifySignedoff PASS 0.13 seconds
GitLint FAIL 0.33 seconds
SubjectPrefix PASS 0.13 seconds
BuildKernel PASS 25.87 seconds
CheckAllWarning PASS 28.73 seconds
CheckSparse PASS 40.08 seconds
BuildKernel32 PASS 30.49 seconds
CheckKernelLLVM SKIP 0.00 seconds
TestRunnerSetup PASS 464.22 seconds
TestRunner_l2cap-tester PASS 62.49 seconds
IncrementalBuild PASS 24.31 seconds
Details
##############################
Test: CheckPatch - FAIL
Desc: Run checkpatch.pl script
Output:
Bluetooth: L2CAP: access chan->conn safely in get/setsockopt
WARNING: Prefer a maximum 75 chars per line (possible unwrapped commit description?)
#86:
Since commit b66774b48dd9 ("Bluetooth: L2CAP: Fix UAF in channel timeout by holding conn ref")
total: 0 errors, 1 warnings, 0 checks, 181 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/14739667.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: access chan->conn safely in get/setsockopt
3: B1 Line exceeds max length (94>80): "Since commit b66774b48dd9 ("Bluetooth: L2CAP: Fix UAF in channel timeout by holding conn ref")"
##############################
Test: CheckKernelLLVM - SKIP
Desc: Build kernel with LLVM + context analysis
Output:
Clang not found
https://github.com/bluez/bluetooth-next/pull/563
---
Regards,
Linux Bluetooth
next prev parent reply other threads:[~2026-08-09 18:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-09 17:42 [PATCH] Bluetooth: L2CAP: access chan->conn safely in get/setsockopt Pauli Virtanen
2026-08-09 18:40 ` bluez.test.bot [this message]
2026-08-11 20:10 ` patchwork-bot+bluetooth
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=6a78c9ab.d6f58ba8.2929e3.eea1@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=pav@iki.fi \
/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.