From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, keescook@chromium.org
Subject: RE: Introduce flexible array struct memcpy() helpers
Date: Tue, 03 May 2022 20:12:09 -0700 (PDT) [thread overview]
Message-ID: <6271ef09.1c69fb81.ec4d5.2112@mx.google.com> (raw)
In-Reply-To: <20220504014440.3697851-2-keescook@chromium.org>
[-- Attachment #1: Type: text/plain, Size: 9911 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=638153
---Test result---
Test Summary:
CheckPatch FAIL 15.45 seconds
GitLint FAIL 7.70 seconds
SubjectPrefix FAIL 28.23 seconds
BuildKernel PASS 36.05 seconds
BuildKernel32 PASS 34.02 seconds
Incremental Build with patchesPASS 324.75 seconds
TestRunner: Setup PASS 541.23 seconds
TestRunner: l2cap-tester PASS 19.53 seconds
TestRunner: bnep-tester PASS 7.22 seconds
TestRunner: mgmt-tester PASS 110.30 seconds
TestRunner: rfcomm-tester PASS 10.98 seconds
TestRunner: sco-tester PASS 10.26 seconds
TestRunner: smp-tester PASS 10.29 seconds
TestRunner: userchan-tester PASS 7.09 seconds
Details
##############################
Test: CheckPatch - FAIL - 15.45 seconds
Run checkpatch.pl script with rule in .checkpatch.conf
[01/32] netlink: Avoid memcpy() across flexible array boundary\WARNING:COMMIT_LOG_LONG_LINE: Possible unwrapped commit description (prefer a maximum 75 chars per line)
#172:
memcpy: detected field-spanning write (size 32) of single field "&errmsg->msg" (size 16)
WARNING:BAD_SIGN_OFF: Non-standard signature: Fixed-by:
#179:
Fixed-by: Rasmus Villemoes <linux@rasmusvillemoes.dk>
total: 0 errors, 2 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/12836836.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.
[02/32] Introduce flexible array struct memcpy() helpers\Traceback (most recent call last):
File "scripts/spdxcheck.py", line 6, in <module>
from ply import lex, yacc
ModuleNotFoundError: No module named 'ply'
WARNING:FILE_PATH_CHANGES: added, moved or deleted file(s), does MAINTAINERS need updating?
#300:
new file mode 100644
ERROR:SPACING: need consistent spacing around '*' (ctx:WxV)
#523: FILE: include/linux/flex_array.h:219:
+ typeof(*(src)) *__fc_src = (src); \
^
ERROR:SPACING: need consistent spacing around '*' (ctx:WxV)
#576: FILE: include/linux/flex_array.h:272:
+ typeof(**(alloc)) *__fd_alloc; \
^
ERROR:SPACING: need consistent spacing around '*' (ctx:WxV)
#754: FILE: include/linux/flex_array.h:450:
+ typeof((*__mtfd_alloc)dot_fas_member) *__mtfd_fas; \
^
ERROR:SPACING: need consistent spacing around '*' (ctx:WxV)
#861: FILE: include/linux/flex_array.h:557:
+ typeof(*(bytes_written)) *__ftm_written = (bytes_written); \
^
ERROR:SPACING: need consistent spacing around '*' (ctx:WxV)
#910: FILE: include/linux/flex_array.h:606:
+ typeof(*(alloc_size)) *__ftmd_alloc_size = (alloc_size); \
^
total: 5 errors, 1 warnings, 662 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/12836837.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.
[03/32] flex_array: Add Kunit tests\Traceback (most recent call last):
File "scripts/spdxcheck.py", line 6, in <module>
from ply import lex, yacc
ModuleNotFoundError: No module named 'ply'
WARNING:CONFIG_DESCRIPTION: please write a paragraph that describes the config symbol fully
#205: FILE: lib/Kconfig.debug:2565:
+config FLEX_ARRAY_KUNIT_TEST
WARNING:FILE_PATH_CHANGES: added, moved or deleted file(s), does MAINTAINERS need updating?
#228:
new file mode 100644
total: 0 errors, 2 warnings, 554 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/12836839.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.
[04/32] fortify: Add run-time WARN for cross-field memcpy()\WARNING:COMMIT_LOG_LONG_LINE: Possible unwrapped commit description (prefer a maximum 75 chars per line)
#178:
memcpy: detected field-spanning write (size N) of single field "var->dest" (size M)
total: 0 errors, 1 warnings, 96 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/12836838.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.
[07/32] iwlwifi: calib: Use mem_to_flex_dup() with struct iwl_calib_result\WARNING:COMMIT_LOG_LONG_LINE: Possible unwrapped commit description (prefer a maximum 75 chars per line)
#176:
memcpy: detected field-spanning write (size 8) of single field "&res->hdr" (size 4)
total: 0 errors, 1 warnings, 0 checks, 29 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/12836846.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 - 7.70 seconds
Run gitlint with rule in .gitlint
[01/32] netlink: Avoid memcpy() across flexible array boundary
7: B1 Line exceeds max length (88>80): "memcpy: detected field-spanning write (size 32) of single field "&errmsg->msg" (size 16)"
15: B1 Line exceeds max length (90>80): "Link: https://lore.kernel.org/lkml/d7251d92-150b-5346-6237-52afc154bb00@rasmusvillemoes.dk"
[02/32] Introduce flexible array struct memcpy() helpers
39: B3 Line contains hard tab characters (\t): " ... /* arbitrary members */"
40: B3 Line contains hard tab characters (\t): " u16 part_count; /* count of elements stored in "parts" below. */"
41: B3 Line contains hard tab characters (\t): " ... /* arbitrary members */"
42: B3 Line contains hard tab characters (\t): " u32 parts[]; /* flexible array with elements of type u32. */"
49: B3 Line contains hard tab characters (\t): " ... /* arbitrary members */"
57: B3 Line contains hard tab characters (\t): " ... /* arbitrary members */"
58: B3 Line contains hard tab characters (\t): " u16 part_count; /* count of elements stored in "parts" below. */"
59: B3 Line contains hard tab characters (\t): " ... /* arbitrary members */"
61: B3 Line contains hard tab characters (\t): " ... /* other blob members */"
[04/32] fortify: Add run-time WARN for cross-field memcpy()
14: B1 Line exceeds max length (85>80): " memcpy: detected field-spanning write (size N) of single field "var->dest" (size M)"
38: B3 Line contains hard tab characters (\t): " void *a;"
39: B3 Line contains hard tab characters (\t): " int b;"
40: B3 Line contains hard tab characters (\t): " size_t array_size;"
41: B3 Line contains hard tab characters (\t): " u32 c;"
42: B3 Line contains hard tab characters (\t): " u8 flex_array[];"
60: B3 Line contains hard tab characters (\t): " int foo;"
61: B3 Line contains hard tab characters (\t): " char bar;"
62: B3 Line contains hard tab characters (\t): " struct normal_flex_array embedded;"
[07/32] iwlwifi: calib: Use mem_to_flex_dup() with struct iwl_calib_result
11: B1 Line exceeds max length (83>80): "memcpy: detected field-spanning write (size 8) of single field "&res->hdr" (size 4)"
##############################
Test: SubjectPrefix - FAIL - 28.23 seconds
Check subject contains "Bluetooth" prefix
"Bluetooth: " is not specified in the subject
"Bluetooth: " is not specified in the subject
"Bluetooth: " is not specified in the subject
"Bluetooth: " is not specified in the subject
"Bluetooth: " is not specified in the subject
"Bluetooth: " is not specified in the subject
"Bluetooth: " is not specified in the subject
"Bluetooth: " is not specified in the subject
"Bluetooth: " is not specified in the subject
"Bluetooth: " is not specified in the subject
"Bluetooth: " is not specified in the subject
"Bluetooth: " is not specified in the subject
"Bluetooth: " is not specified in the subject
"Bluetooth: " is not specified in the subject
"Bluetooth: " is not specified in the subject
"Bluetooth: " is not specified in the subject
"Bluetooth: " is not specified in the subject
"Bluetooth: " is not specified in the subject
"Bluetooth: " is not specified in the subject
"Bluetooth: " is not specified in the subject
"Bluetooth: " is not specified in the subject
"Bluetooth: " is not specified in the subject
"Bluetooth: " is not specified in the subject
"Bluetooth: " is not specified in the subject
"Bluetooth: " is not specified in the subject
"Bluetooth: " is not specified in the subject
"Bluetooth: " is not specified in the subject
"Bluetooth: " is not specified in the subject
"Bluetooth: " is not specified in the subject
"Bluetooth: " is not specified in the subject
"Bluetooth: " is not specified in the subject
---
Regards,
Linux Bluetooth
next prev parent reply other threads:[~2022-05-04 3:12 UTC|newest]
Thread overview: 71+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-04 1:44 [PATCH 00/32] Introduce flexible array struct memcpy() helpers Kees Cook
2022-05-04 1:44 ` [PATCH 01/32] netlink: Avoid memcpy() across flexible array boundary Kees Cook
2022-05-04 3:12 ` bluez.test.bot [this message]
2022-05-04 3:31 ` Gustavo A. R. Silva
2022-05-04 3:37 ` Kees Cook
2022-05-04 1:44 ` [PATCH 02/32] Introduce flexible array struct memcpy() helpers Kees Cook
2022-05-04 7:25 ` Johannes Berg
2022-05-04 15:38 ` Kees Cook
2022-05-04 16:08 ` David Laight
2022-05-05 13:16 ` Johannes Berg
2022-05-05 15:16 ` Keith Packard
2022-05-05 19:32 ` Kees Cook
2022-05-05 20:08 ` Keith Packard
2022-05-05 20:12 ` Johannes Berg
2022-05-06 11:15 ` David Laight
2022-05-06 11:15 ` David Laight
2022-05-05 19:27 ` Kees Cook
2022-05-04 1:44 ` [PATCH 03/32] flex_array: Add Kunit tests Kees Cook
2022-05-04 3:00 ` David Gow
2022-05-04 19:43 ` Kees Cook
2022-05-04 19:58 ` Daniel Latypov
2022-05-04 1:44 ` [PATCH 04/32] fortify: Add run-time WARN for cross-field memcpy() Kees Cook
2022-05-04 1:44 ` [PATCH 05/32] brcmfmac: Use mem_to_flex_dup() with struct brcmf_fweh_queue_item Kees Cook
2022-05-16 12:49 ` Arend van Spriel
2022-05-17 3:57 ` Kees Cook
2022-05-04 1:44 ` [PATCH 06/32] iwlwifi: calib: Prepare to use mem_to_flex_dup() Kees Cook
2022-05-04 1:44 ` [PATCH 07/32] iwlwifi: calib: Use mem_to_flex_dup() with struct iwl_calib_result Kees Cook
2022-05-04 1:44 ` [PATCH 08/32] iwlwifi: mvm: Use mem_to_flex_dup() with struct ieee80211_key_conf Kees Cook
2022-05-04 1:44 ` [PATCH 09/32] p54: Use mem_to_flex_dup() with struct p54_cal_database Kees Cook
2022-05-04 1:44 ` [PATCH 10/32] wcn36xx: Use mem_to_flex_dup() with struct wcn36xx_hal_ind_msg Kees Cook
2022-05-04 5:42 ` Kalle Valo
2022-05-04 15:08 ` Kees Cook
2022-05-04 1:44 ` [PATCH 11/32] nl80211: Use mem_to_flex_dup() with struct cfg80211_cqm_config Kees Cook
2022-05-04 1:44 ` [PATCH 12/32] cfg80211: Use mem_to_flex_dup() with struct cfg80211_bss_ies Kees Cook
2022-05-04 7:28 ` Johannes Berg
2022-05-04 15:13 ` Kees Cook
2022-05-04 1:44 ` [PATCH 13/32] mac80211: Use mem_to_flex_dup() with several structs Kees Cook
2022-05-04 1:44 ` [PATCH 14/32] af_unix: Use mem_to_flex_dup() with struct unix_address Kees Cook
2022-05-04 1:44 ` [PATCH 15/32] 802/garp: Use mem_to_flex_dup() with struct garp_attr Kees Cook
2022-05-04 1:44 ` [PATCH 16/32] 802/mrp: Use mem_to_flex_dup() with struct mrp_attr Kees Cook
2022-05-04 1:44 ` [PATCH 17/32] net/flow_offload: Use mem_to_flex_dup() with struct flow_action_cookie Kees Cook
2022-05-04 1:44 ` [PATCH 18/32] firewire: Use __mem_to_flex_dup() with struct iso_interrupt_event Kees Cook
2022-05-04 1:44 ` [PATCH 19/32] afs: Use mem_to_flex_dup() with struct afs_acl Kees Cook
2022-05-04 1:44 ` [PATCH 20/32] ASoC: sigmadsp: Use mem_to_flex_dup() with struct sigmadsp_data Kees Cook
2022-05-04 15:17 ` Mark Brown
2022-05-04 1:44 ` [PATCH 21/32] soc: qcom: apr: Use mem_to_flex_dup() with struct apr_rx_buf Kees Cook
2022-05-04 1:44 ` [PATCH 22/32] atags_proc: Use mem_to_flex_dup() with struct buffer Kees Cook
2022-05-04 1:44 ` [PATCH 23/32] Bluetooth: Use mem_to_flex_dup() with struct hci_op_configure_data_path Kees Cook
2022-05-04 1:44 ` [PATCH 24/32] IB/hfi1: Use mem_to_flex_dup() for struct tid_rb_node Kees Cook
2022-05-04 1:44 ` [PATCH 25/32] Drivers: hv: utils: Use mem_to_flex_dup() with struct cn_msg Kees Cook
2022-05-04 1:44 ` [PATCH 26/32] ima: Use mem_to_flex_dup() with struct modsig Kees Cook
2022-05-04 1:44 ` [PATCH 27/32] KEYS: Use mem_to_flex_dup() with struct user_key_payload Kees Cook
2022-05-04 1:44 ` [PATCH 28/32] selinux: Use mem_to_flex_dup() with xfrm and sidtab Kees Cook
2022-05-04 22:57 ` Paul Moore
2022-05-04 23:43 ` Gustavo A. R. Silva
2022-05-05 3:14 ` Paul Moore
2022-05-05 18:39 ` Kees Cook
2022-05-05 23:16 ` Paul Moore
2022-05-06 1:08 ` Gustavo A. R. Silva
2022-05-04 1:44 ` [PATCH 29/32] xtensa: Use mem_to_flex_dup() with struct property Kees Cook
2022-05-04 18:09 ` Rob Herring
2022-05-04 18:09 ` Rob Herring
2022-05-04 1:44 ` [PATCH 30/32] usb: gadget: f_fs: Use mem_to_flex_dup() with struct ffs_buffer Kees Cook
2022-05-04 1:44 ` [PATCH 31/32] xenbus: Use mem_to_flex_dup() with struct read_buffer Kees Cook
2022-05-04 1:44 ` [PATCH 32/32] esas2r: Use __mem_to_flex() with struct atto_ioctl Kees Cook
2022-05-12 21:41 ` [PATCH 19/32] afs: Use mem_to_flex_dup() with struct afs_acl David Howells
2022-05-12 21:41 ` David Howells
2022-05-13 15:44 ` Kees Cook
2022-05-13 15:44 ` Kees Cook
2022-05-12 21:47 ` [PATCH 00/32] Introduce flexible array struct memcpy() helpers David Howells
2022-05-12 21:47 ` David Howells
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=6271ef09.1c69fb81.ec4d5.2112@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=keescook@chromium.org \
--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 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.