From: kernel test robot <lkp@intel.com>
To: kbuild-all@lists.01.org
Subject: [android-common:android-4.19 1/5] fs/incfs/integrity.c:196:9: sparse: sparse: Variable length array is used.
Date: Sat, 26 Jun 2021 18:13:42 +0800 [thread overview]
Message-ID: <202106261840.nnr6fxGP-lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 3266 bytes --]
tree: https://android.googlesource.com/kernel/common android-4.19
head: cd46498a220773ccff35104a8de2463adf761267
commit: 040942fc50b20325bb56737c32b303268bb6f35c [1/5] ANDROID: Initial commit of Incremental FS
config: i386-randconfig-s002-20210625 (attached as .config)
compiler: gcc-9 (Debian 9.3.0-22) 9.3.0
reproduce:
# apt-get install sparse
# sparse version: v0.6.3-341-g8af24329-dirty
git remote add android-common https://android.googlesource.com/kernel/common
git fetch --no-tags android-common android-4.19
git checkout 040942fc50b20325bb56737c32b303268bb6f35c
# save the attached .config to linux build tree
make W=1 C=1 CF='-fdiagnostic-prefix -D__CHECK_ENDIAN__' W=1 ARCH=i386
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>
sparse warnings: (new ones prefixed by >>)
>> fs/incfs/integrity.c:196:9: sparse: sparse: Variable length array is used.
In file included from include/linux/kernel.h:14,
from include/linux/crypto.h:21,
from include/crypto/hash.h:16,
from fs/incfs/integrity.c:6:
fs/incfs/integrity.c: In function 'incfs_validate_pkcs7_signature':
include/linux/kern_levels.h:5:18: warning: format '%ld' expects argument of type 'long int', but argument 3 has type 'size_t' {aka 'unsigned int'} [-Wformat=]
5 | #define KERN_SOH "001" /* ASCII Start Of Header */
| ^~~~~~
include/linux/printk.h:136:10: note: in definition of macro 'no_printk'
136 | printk(fmt, ##__VA_ARGS__); 12- | ^~~
include/linux/kern_levels.h:15:20: note: in expansion of macro 'KERN_SOH'
15 | #define KERN_DEBUG KERN_SOH "7" /* debug-level messages */
| ^~~~~~~~
include/linux/printk.h:346:12: note: in expansion of macro 'KERN_DEBUG'
346 | no_printk(KERN_DEBUG pr_fmt(fmt), ##__VA_ARGS__)
| ^~~~~~~~~~
fs/incfs/integrity.c:24:3: note: in expansion of macro 'pr_debug'
24 | pr_debug("PKCS#7 parsing error. ptr=%p size=%ld err=%ldn",
| ^~~~~~~~
fs/incfs/integrity.c:24:49: note: format string is defined here
24 | pr_debug("PKCS#7 parsing error. ptr=%p size=%ld err=%ldn",
| ~~^
| |
| long int
| %d
vim +196 fs/incfs/integrity.c
192
193 int incfs_calc_digest(struct incfs_hash_alg *alg, struct mem_range data,
194 struct mem_range digest)
195 {
> 196 SHASH_DESC_ON_STACK(desc, alg->shash);
197
198 if (!alg || !alg->shash || !data.data || !digest.data)
199 return -EFAULT;
200
201 if (alg->digest_size > digest.len)
202 return -EINVAL;
203
204 desc->tfm = alg->shash;
205 return crypto_shash_digest(desc, data.data, data.len, digest.data);
206 }
207
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all(a)lists.01.org
[-- Attachment #2: config.gz --]
[-- Type: application/gzip, Size: 32769 bytes --]
next reply other threads:[~2021-06-26 10:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-26 10:13 kernel test robot [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-05-04 12:37 [android-common:android-4.19 1/5] fs/incfs/integrity.c:196:9: sparse: sparse: Variable length array is used kernel test robot
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=202106261840.nnr6fxGP-lkp@intel.com \
--to=lkp@intel.com \
--cc=kbuild-all@lists.01.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.