From: kernel test robot <lkp@intel.com>
To: kbuild-all@lists.01.org
Subject: [block:wq-no-manager 18/18] fs/io-wq.c:290:23: sparse: sparse: incorrect type in argument 1 (different base types)
Date: Tue, 09 Mar 2021 07:05:25 +0800 [thread overview]
Message-ID: <202103090721.IVaxtf7J-lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2555 bytes --]
tree: https://git.kernel.org/pub/scm/linux/kernel/git/axboe/linux-block.git wq-no-manager
head: a91ab2dfc03aad93bc21a6aec7cf7a52236ca1d7
commit: a91ab2dfc03aad93bc21a6aec7cf7a52236ca1d7 [18/18] io-wq: eliminate the need for a manager thread
config: i386-randconfig-s001-20210309 (attached as .config)
compiler: gcc-9 (Debian 9.3.0-22) 9.3.0
reproduce:
# apt-get install sparse
# sparse version: v0.6.3-262-g5e674421-dirty
# https://git.kernel.org/pub/scm/linux/kernel/git/axboe/linux-block.git/commit/?id=a91ab2dfc03aad93bc21a6aec7cf7a52236ca1d7
git remote add block https://git.kernel.org/pub/scm/linux/kernel/git/axboe/linux-block.git
git fetch --no-tags block wq-no-manager
git checkout a91ab2dfc03aad93bc21a6aec7cf7a52236ca1d7
# save the attached .config to linux build tree
make W=1 C=1 CF='-fdiagnostic-prefix -D__CHECK_ENDIAN__' 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/io-wq.c:290:23: sparse: sparse: incorrect type in argument 1 (different base types) @@ expected unsigned int [usertype] size @@ got restricted gfp_t @@
fs/io-wq.c:290:23: sparse: expected unsigned int [usertype] size
fs/io-wq.c:290:23: sparse: got restricted gfp_t
>> fs/io-wq.c:290:35: sparse: sparse: incorrect type in argument 2 (different base types) @@ expected restricted gfp_t [usertype] flags @@ got unsigned int @@
fs/io-wq.c:290:35: sparse: expected restricted gfp_t [usertype] flags
fs/io-wq.c:290:35: sparse: got unsigned int
vim +290 fs/io-wq.c
284
285 static void io_queue_worker_create(struct io_wqe *wqe, struct io_wqe_acct *acct)
286 {
287 struct create_worker_data *cwd;
288 int ret;
289
> 290 cwd = kmalloc(GFP_ATOMIC, sizeof(*cwd));
291 if (unlikely(!cwd))
292 return;
293
294 atomic_inc(&acct->nr_running);
295 atomic_inc(&wqe->wq->worker_refs);
296 init_task_work(&cwd->work, create_worker_cb);
297 cwd->wqe = wqe;
298 cwd->index = acct->index;
299 ret = task_work_add(wqe->wq->task, &cwd->work, TWA_SIGNAL);
300 if (ret) {
301 if (atomic_dec_and_test(&wqe->wq->worker_refs))
302 complete(&wqe->wq->worker_done);
303 kfree(cwd);
304 }
305 }
306
---
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: 38542 bytes --]
reply other threads:[~2021-03-08 23:05 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=202103090721.IVaxtf7J-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.