From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, coelacanthushex@gmail.com
Subject: RE: monitor: fix buffer overflow when terminal width > 255
Date: Sat, 14 Sep 2024 09:02:37 -0700 (PDT) [thread overview]
Message-ID: <66e5b39d.050a0220.34073d.206c@mx.google.com> (raw)
In-Reply-To: <20240914-fix-log-buffer-overflow-v1-1-733cb4fff673@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1579 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=890395
---Test result---
Test Summary:
CheckPatch PASS 0.49 seconds
GitLint PASS 0.35 seconds
BuildEll PASS 24.73 seconds
BluezMake PASS 1696.44 seconds
MakeCheck PASS 13.31 seconds
MakeDistcheck PASS 179.41 seconds
CheckValgrind PASS 256.32 seconds
CheckSmatch WARNING 358.63 seconds
bluezmakeextell PASS 120.73 seconds
IncrementalBuild PASS 1407.21 seconds
ScanBuild WARNING 1016.29 seconds
Details
##############################
Test: CheckSmatch - WARNING
Desc: Run smatch tool with source
Output:
monitor/packet.c: note: in included file:monitor/display.h:82:26: warning: Variable length array is used.monitor/packet.c:1868:26: warning: Variable length array is used.monitor/packet.c: note: in included file:monitor/bt.h:3606:52: warning: array of flexible structuresmonitor/bt.h:3594:40: warning: array of flexible structures
##############################
Test: ScanBuild - WARNING
Desc: Run Scan Build
Output:
monitor/packet.c:529:1: warning: Potential leak of memory pointed to by 'line'
}
^
1 warning generated.
---
Regards,
Linux Bluetooth
next prev parent reply other threads:[~2024-09-14 16:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-14 14:09 [PATCH] monitor: fix buffer overflow when terminal width > 255 Celeste Liu
2024-09-14 16:02 ` bluez.test.bot [this message]
2024-09-14 16:12 ` Celeste Liu
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=66e5b39d.050a0220.34073d.206c@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=coelacanthushex@gmail.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox