From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, luiz.dentz@gmail.com
Subject: RE: [BlueZ,v1,1/3] avrcp: Fix out-of-bounds parsing of ListPlayerAttributes response
Date: Fri, 28 Aug 2026 15:20:41 -0700 (PDT) [thread overview]
Message-ID: <6a9209b9.bb286e2c.950c9.553c@mx.google.com> (raw)
In-Reply-To: <20260828161702.519421-1-luiz.dentz@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2062 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=1153367
---Test result---
Test Summary:
CheckPatch FAIL 1.48 seconds
GitLint PASS 0.82 seconds
BuildEll PASS 18.38 seconds
BluezMake PASS 660.03 seconds
MakeCheck PASS 3.19 seconds
MakeDistcheck PASS 146.90 seconds
CheckValgrind PASS 151.18 seconds
CheckSmatch PASS 278.03 seconds
bluezmakeextell PASS 95.58 seconds
IncrementalBuild PASS 675.82 seconds
ScanBuild PASS 902.64 seconds
Details
##############################
Test: CheckPatch - FAIL
Desc: Run checkpatch.pl script
Output:
[BlueZ,v1,1/3] avrcp: Fix out-of-bounds parsing of ListPlayerAttributes response
ERROR:BAD_SIGN_OFF: Unrecognized email address: '@ax-nnlabs'
#121:
Reported-by: @ax-nnlabs
WARNING:COMMIT_LOG_LONG_LINE: Possible unwrapped commit description (prefer a maximum 75 chars per line)
#122:
Closes: https://github.com/bluez/bluez/security/advisories/GHSA-m2vx-pw5f-rc8v
/github/workspace/src/patch/14773935.patch total: 1 errors, 1 warnings, 56 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/14773935.patch has style problems, please review.
NOTE: Ignored message types: COMMIT_MESSAGE COMPLEX_MACRO CONST_STRUCT FILE_PATH_CHANGES MISSING_SIGN_OFF PREFER_PACKED SPDX_LICENSE_TAG SPLIT_STRING SSCANF_TO_KSTRTO
NOTE: If any of the errors are false positives, please report
them to the maintainer, see CHECKPATCH in MAINTAINERS.
https://github.com/bluez/bluez/pull/2448
---
Regards,
Linux Bluetooth
prev parent reply other threads:[~2026-08-28 22:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-28 16:17 [PATCH BlueZ v1 1/3] avrcp: Fix out-of-bounds parsing of ListPlayerAttributes response Luiz Augusto von Dentz
2026-08-28 16:17 ` [PATCH BlueZ v1 2/3] avrcp: Fix out-of-bounds read parsing attribute lists Luiz Augusto von Dentz
2026-08-28 16:17 ` [PATCH BlueZ v1 3/3] avrcp: Use util_iov helpers to parse responses Luiz Augusto von Dentz
2026-08-28 22:20 ` 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=6a9209b9.bb286e2c.950c9.553c@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=luiz.dentz@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox