From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, palmer@rivosinc.com
Subject: RE: Bluetooth: L2CAP: Elide a string overflow warning
Date: Fri, 12 Aug 2022 00:13:36 -0700 (PDT) [thread overview]
Message-ID: <62f5fda0.050a0220.ebb71.24fe@mx.google.com> (raw)
In-Reply-To: <20220812055249.8037-1-palmer@rivosinc.com>
[-- Attachment #1: Type: text/plain, Size: 6064 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=667062
---Test result---
Test Summary:
CheckPatch FAIL 1.60 seconds
GitLint FAIL 1.01 seconds
SubjectPrefix PASS 0.84 seconds
BuildKernel PASS 41.49 seconds
BuildKernel32 PASS 34.89 seconds
Incremental Build with patchesPASS 50.21 seconds
TestRunner: Setup PASS 605.56 seconds
TestRunner: l2cap-tester PASS 20.02 seconds
TestRunner: bnep-tester PASS 8.10 seconds
TestRunner: mgmt-tester PASS 122.17 seconds
TestRunner: rfcomm-tester PASS 11.73 seconds
TestRunner: sco-tester PASS 11.48 seconds
TestRunner: smp-tester PASS 12.14 seconds
TestRunner: userchan-tester PASS 8.96 seconds
Details
##############################
Test: CheckPatch - FAIL - 1.60 seconds
Run checkpatch.pl script with rule in .checkpatch.conf
Bluetooth: L2CAP: Elide a string overflow warning\WARNING:COMMIT_LOG_LONG_LINE: Possible unwrapped commit description (prefer a maximum 75 chars per line)
#88:
In file included from /scratch/merges/ko-linux-next/linux/include/linux/string.h:253,
WARNING:USE_RELATIVE_PATH: use relative pathname instead of absolute in changelog text
#95:
from /scratch/merges/ko-linux-next/linux/net/bluetooth/l2cap_core.c:31:
WARNING:USE_RELATIVE_PATH: use relative pathname instead of absolute in changelog text
#98:
inlined from 'l2cap_global_chan_by_psm' at /scratch/merges/ko-linux-next/linux/net/bluetooth/l2cap_core.c:2003:15:
WARNING:USE_RELATIVE_PATH: use relative pathname instead of absolute in changelog text
#99:
/scratch/merges/ko-linux-next/linux/include/linux/fortify-string.h:44:33: error: '__builtin_memcmp' specified bound 6 exceeds source size 0 [-Werror=stringop-overread]
WARNING:USE_RELATIVE_PATH: use relative pathname instead of absolute in changelog text
#102:
/scratch/merges/ko-linux-next/linux/include/linux/fortify-string.h:420:16: note: in expansion of macro '__underlying_memcmp'
WARNING:USE_RELATIVE_PATH: use relative pathname instead of absolute in changelog text
#107:
inlined from 'l2cap_global_chan_by_psm' at /scratch/merges/ko-linux-next/linux/net/bluetooth/l2cap_core.c:2004:15:
WARNING:USE_RELATIVE_PATH: use relative pathname instead of absolute in changelog text
#108:
/scratch/merges/ko-linux-next/linux/include/linux/fortify-string.h:44:33: error: '__builtin_memcmp' specified bound 6 exceeds source size 0 [-Werror=stringop-overread]
WARNING:USE_RELATIVE_PATH: use relative pathname instead of absolute in changelog text
#111:
/scratch/merges/ko-linux-next/linux/include/linux/fortify-string.h:420:16: note: in expansion of macro '__underlying_memcmp'
total: 0 errors, 8 warnings, 0 checks, 18 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/12941909.patch has style problems, please review.
NOTE: Ignored message types: UNKNOWN_COMMIT_ID
NOTE: If any of the errors are false positives, please report
them to the maintainer, see CHECKPATCH in MAINTAINERS.
##############################
Test: GitLint - FAIL - 1.01 seconds
Run gitlint with rule in .gitlint
Bluetooth: L2CAP: Elide a string overflow warning
9: B1 Line exceeds max length (85>80): "In file included from /scratch/merges/ko-linux-next/linux/include/linux/string.h:253,"
10: B1 Line exceeds max length (84>80): " from /scratch/merges/ko-linux-next/linux/include/linux/bitmap.h:11,"
11: B1 Line exceeds max length (85>80): " from /scratch/merges/ko-linux-next/linux/include/linux/cpumask.h:12,"
12: B1 Line exceeds max length (91>80): " from /scratch/merges/ko-linux-next/linux/include/linux/mm_types_task.h:14,"
13: B1 Line exceeds max length (85>80): " from /scratch/merges/ko-linux-next/linux/include/linux/mm_types.h:5,"
14: B1 Line exceeds max length (84>80): " from /scratch/merges/ko-linux-next/linux/include/linux/buildid.h:5,"
15: B1 Line exceeds max length (84>80): " from /scratch/merges/ko-linux-next/linux/include/linux/module.h:14,"
16: B1 Line exceeds max length (88>80): " from /scratch/merges/ko-linux-next/linux/net/bluetooth/l2cap_core.c:31:"
18: B1 Line exceeds max length (104>80): " inlined from 'bacmp' at /scratch/merges/ko-linux-next/linux/include/net/bluetooth/bluetooth.h:347:9,"
19: B1 Line exceeds max length (118>80): " inlined from 'l2cap_global_chan_by_psm' at /scratch/merges/ko-linux-next/linux/net/bluetooth/l2cap_core.c:2003:15:"
20: B1 Line exceeds max length (167>80): "/scratch/merges/ko-linux-next/linux/include/linux/fortify-string.h:44:33: error: '__builtin_memcmp' specified bound 6 exceeds source size 0 [-Werror=stringop-overread]"
23: B1 Line exceeds max length (124>80): "/scratch/merges/ko-linux-next/linux/include/linux/fortify-string.h:420:16: note: in expansion of macro '__underlying_memcmp'"
27: B1 Line exceeds max length (104>80): " inlined from 'bacmp' at /scratch/merges/ko-linux-next/linux/include/net/bluetooth/bluetooth.h:347:9,"
28: B1 Line exceeds max length (118>80): " inlined from 'l2cap_global_chan_by_psm' at /scratch/merges/ko-linux-next/linux/net/bluetooth/l2cap_core.c:2004:15:"
29: B1 Line exceeds max length (167>80): "/scratch/merges/ko-linux-next/linux/include/linux/fortify-string.h:44:33: error: '__builtin_memcmp' specified bound 6 exceeds source size 0 [-Werror=stringop-overread]"
32: B1 Line exceeds max length (124>80): "/scratch/merges/ko-linux-next/linux/include/linux/fortify-string.h:420:16: note: in expansion of macro '__underlying_memcmp'"
---
Regards,
Linux Bluetooth
next prev parent reply other threads:[~2022-08-12 7:13 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-12 5:52 [PATCH] Bluetooth: L2CAP: Elide a string overflow warning Palmer Dabbelt
2022-08-12 7:13 ` bluez.test.bot [this message]
2022-08-12 18:08 ` Luiz Augusto von Dentz
2022-08-12 18:50 ` Palmer Dabbelt
2022-08-25 11:01 ` [PATCH] " Siddh Raman Pant
2022-08-29 19:51 ` Elliott, Robert (Servers)
2022-09-01 7:44 ` Siddh Raman Pant
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=62f5fda0.050a0220.ebb71.24fe@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=palmer@rivosinc.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.