From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, vinit.mehta@nxp.com
Subject: RE: mgmt: Fix crash after pair command
Date: Thu, 14 Dec 2023 04:05:15 -0800 (PST) [thread overview]
Message-ID: <657aef7b.050a0220.d6086.d239@mx.google.com> (raw)
In-Reply-To: <20231214110339.1763-2-vinit.mehta@nxp.com>
[-- Attachment #1: Type: text/plain, Size: 4029 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=810016
---Test result---
Test Summary:
CheckPatch FAIL 0.82 seconds
GitLint PASS 0.30 seconds
BuildEll PASS 24.46 seconds
BluezMake PASS 735.10 seconds
MakeCheck PASS 12.45 seconds
MakeDistcheck PASS 154.37 seconds
CheckValgrind PASS 216.05 seconds
CheckSmatch PASS 319.72 seconds
bluezmakeextell PASS 100.78 seconds
IncrementalBuild PASS 667.31 seconds
ScanBuild WARNING 915.38 seconds
Details
##############################
Test: CheckPatch - FAIL
Desc: Run checkpatch.pl script
Output:
[BlueZ,v1,1/1] mgmt: Fix crash after pair command
ERROR:OPEN_BRACE: that open brace { should be on the previous line
#117: FILE: client/mgmt.c:853:
+ if(len)
+ {
ERROR:SPACING: space required before the open parenthesis '('
#117: FILE: client/mgmt.c:853:
+ if(len)
WARNING:LONG_LINE: line length of 83 exceeds 80 columns
#122: FILE: client/mgmt.c:858:
+ mgmt_confirm_neg_reply(prompt.index, &prompt.addr);
ERROR:OPEN_BRACE: that open brace { should be on the previous line
#124: FILE: client/mgmt.c:860:
else
+ {
WARNING:LONG_LINE_COMMENT: line length of 87 exceeds 80 columns
#126: FILE: client/mgmt.c:862:
+ /* After pair command, if the user doesn't provide any input on
WARNING:LONG_LINE_COMMENT: line length of 89 exceeds 80 columns
#127: FILE: client/mgmt.c:863:
+ * bluetoothctl CLI interface after receiving the prompt(yes/no),
WARNING:LONG_LINE_COMMENT: line length of 82 exceeds 80 columns
#128: FILE: client/mgmt.c:864:
+ * than subsequent CLI command will trigger a call to DBUS
WARNING:LONG_LINE_COMMENT: line length of 83 exceeds 80 columns
#129: FILE: client/mgmt.c:865:
+ * library function (dbus_message_get_no_reply) with a NULL
WARNING:LONG_LINE_COMMENT: line length of 83 exceeds 80 columns
#130: FILE: client/mgmt.c:866:
+ * message pointer which triggers assertion in DBUS library
WARNING:LONG_LINE_COMMENT: line length of 86 exceeds 80 columns
#131: FILE: client/mgmt.c:867:
+ * causing the bluetoothctl process to crash. The change below
WARNING:LONG_LINE_COMMENT: line length of 82 exceeds 80 columns
#132: FILE: client/mgmt.c:868:
+ * will ensure in case if no input is given by the user, a
WARNING:LONG_LINE_COMMENT: line length of 83 exceeds 80 columns
#133: FILE: client/mgmt.c:869:
+ * conditional check is added to handle this scenario and a
WARNING:LONG_LINE_COMMENT: line length of 84 exceeds 80 columns
#134: FILE: client/mgmt.c:870:
+ * default character ('N') will be passed so as to avoid the
WARNING:BLOCK_COMMENT_STYLE: Block comments use a trailing */ on a separate line
#135: FILE: client/mgmt.c:871:
+ * assertion.*/
/github/workspace/src/src/13492807.patch total: 3 errors, 11 warnings, 37 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/src/13492807.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.
##############################
Test: ScanBuild - WARNING
Desc: Run Scan Build
Output:
client/mgmt.c:872:4: warning: Value stored to 'input' is never read
input = dummy_input;
^ ~~~~~~~~~~~
1 warning generated.
---
Regards,
Linux Bluetooth
next prev parent reply other threads:[~2023-12-14 12:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-14 11:03 [PATCH BlueZ v1 0/1] mgmt: Fix crash after pair command Vinit Mehta
2023-12-14 11:03 ` [PATCH BlueZ v1 1/1] " Vinit Mehta
2023-12-14 12:05 ` bluez.test.bot [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-12-19 6:28 [PATCH BlueZ v2 " Vinit Mehta
2023-12-19 7:33 ` bluez.test.bot
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=657aef7b.050a0220.d6086.d239@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=vinit.mehta@nxp.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 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.