From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, hadess@hadess.net
Subject: RE: [BlueZ] obexd: Fix memory leak
Date: Thu, 16 May 2024 08:40:55 -0700 (PDT) [thread overview]
Message-ID: <66462907.050a0220.d27c0.fd63@mx.google.com> (raw)
In-Reply-To: <20240516134053.102475-1-hadess@hadess.net>
[-- Attachment #1: Type: text/plain, Size: 2056 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=853719
---Test result---
Test Summary:
CheckPatch PASS 0.46 seconds
GitLint FAIL 0.51 seconds
BuildEll PASS 24.81 seconds
BluezMake PASS 1701.13 seconds
MakeCheck PASS 13.71 seconds
MakeDistcheck PASS 179.04 seconds
CheckValgrind PASS 250.72 seconds
CheckSmatch PASS 356.39 seconds
bluezmakeextell PASS 120.95 seconds
IncrementalBuild PASS 1481.59 seconds
ScanBuild PASS 1015.99 seconds
Details
##############################
Test: GitLint - FAIL
Desc: Run gitlint
Output:
[BlueZ] obexd: Fix memory leak
WARNING: I3 - ignore-body-lines: gitlint will be switching from using Python regex 'match' (match beginning) to 'search' (match anywhere) semantics. Please review your ignore-body-lines.regex option accordingly. To remove this warning, set general.regex-style-search=True. More details: https://jorisroovers.github.io/gitlint/configuration/#regex-style-search
8: B1 Line exceeds max length (121>80): "bluez-5.75/obexd/plugins/filesystem.c:411:3: alloc_arg: "g_file_get_contents" allocates memory that is stored into "buf"."
9: B1 Line exceeds max length (115>80): "bluez-5.75/obexd/plugins/filesystem.c:418:3: noescape: Resource "buf" is not freed or pointed-to in "g_string_new"."
10: B1 Line exceeds max length (126>80): "bluez-5.75/obexd/plugins/filesystem.c:440:2: leaked_storage: Variable "buf" going out of scope leaks the storage it points to."
11: B3 Line contains hard tab characters (\t): "438| *err = 0;"
13: B3 Line contains hard tab characters (\t): "440|-> return object;"
---
Regards,
Linux Bluetooth
next prev parent reply other threads:[~2024-05-16 15:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-16 13:40 [BlueZ] obexd: Fix memory leak Bastien Nocera
2024-05-16 15:40 ` bluez.test.bot [this message]
2024-05-17 14:50 ` 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=66462907.050a0220.d27c0.fd63@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=hadess@hadess.net \
--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