From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, zuohongsheng@kylinos.cn
Subject: RE: [v2] gatt-server: Fix integer overflow
Date: Thu, 10 Sep 2026 11:25:19 -0700 (PDT) [thread overview]
Message-ID: <6aa2f60f.a86f48e9.3a86da.508d@mx.google.com> (raw)
In-Reply-To: <20260821033214.82863-1-zuohongsheng@kylinos.cn>
[-- Attachment #1: Type: text/plain, Size: 1723 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/1149440/
---Test result---
Test Summary:
CheckPatch PASS 0.46 seconds
GitLint PASS 0.32 seconds
BuildEll PASS 19.47 seconds
BluezMake PASS 354.38 seconds
MakeCheck PASS 6.89 seconds
MakeDistcheck PASS 140.18 seconds
CheckValgrind PASS 145.94 seconds
CheckSmatch WARNING 277.41 seconds
bluezmakeextell PASS 90.59 seconds
IncrementalBuild PASS 368.91 seconds
ScanBuild PASS 1032.26 seconds
Details
##############################
Test: CheckSmatch - WARNING
Desc: Run smatch tool with source
Output:
src/shared/gatt-server.c:271:25: warning: Variable length array is used.src/shared/gatt-server.c:614:25: warning: Variable length array is used.src/shared/gatt-server.c:712:25: warning: Variable length array is used.src/shared/gatt-server.c:271:25: warning: Variable length array is used.src/shared/gatt-server.c:614:25: warning: Variable length array is used.src/shared/gatt-server.c:712:25: warning: Variable length array is used.src/shared/gatt-server.c:271:25: warning: Variable length array is used.src/shared/gatt-server.c:614:25: warning: Variable length array is used.src/shared/gatt-server.c:712:25: warning: Variable length array is used.
https://github.com/bluez/bluez/pull/2512
---
Regards,
Linux Bluetooth
prev parent reply other threads:[~2026-09-10 18:25 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-23 8:42 [PATCH BlueZ] gatt-server: Fix integer overflow zuohsh
2026-07-23 9:58 ` [BlueZ] " bluez.test.bot
2026-08-21 3:31 ` [PATCH v2] " zuohsh
2026-08-21 4:46 ` [v2] " bluez.test.bot
2026-08-21 7:35 ` [PATCH v3] gatt-server: Fix integer overflow and 3 CI VLA wanings zuohsh
2026-08-21 8:42 ` [v3] " bluez.test.bot
2026-08-21 10:40 ` [PATCH v3] " zuohsh
2026-08-21 11:51 ` [v3] " bluez.test.bot
2026-09-10 18:30 ` bluez.test.bot
2026-09-10 18:25 ` 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=6aa2f60f.a86f48e9.3a86da.508d@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=zuohongsheng@kylinos.cn \
/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.