From: kernel test robot <lkp@intel.com>
To: cros-kernel-buildreports@googlegroups.com
Cc: oe-kbuild-all@lists.linux.dev
Subject: [android-common:android12-5.10 4/7] block/blk-flush.c:484:65: sparse: sparse: incorrect type in argument 3 (different base types)
Date: Sun, 24 Nov 2024 23:54:46 +0800 [thread overview]
Message-ID: <202411242320.mzLEc6eU-lkp@intel.com> (raw)
tree: https://android.googlesource.com/kernel/common android12-5.10
head: 894861d67a0f883c2fa20a8ce58634c15d0a27dd
commit: f76294a6557b6c99c9ca58d89232171cf693eac2 [4/7] ANDROID: add hooks into blk-flush.c for customized I/O scheduler
config: x86_64-randconfig-121-20241114 (https://download.01.org/0day-ci/archive/20241124/202411242320.mzLEc6eU-lkp@intel.com/config)
compiler: gcc-12 (Debian 12.2.0-14) 12.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20241124/202411242320.mzLEc6eU-lkp@intel.com/reproduce)
If you fix the issue in a separate patch/commit (i.e. not just a new version of
the same patch/commit), kindly add following tags
| Reported-by: kernel test robot <lkp@intel.com>
| Closes: https://lore.kernel.org/oe-kbuild-all/202411242320.mzLEc6eU-lkp@intel.com/
sparse warnings: (new ones prefixed by >>)
>> block/blk-flush.c:484:65: sparse: sparse: incorrect type in argument 3 (different base types) @@ expected int flags @@ got restricted gfp_t [usertype] flags @@
block/blk-flush.c:484:65: sparse: expected int flags
block/blk-flush.c:484:65: sparse: got restricted gfp_t [usertype] flags
vim +484 block/blk-flush.c
469
470 #include <trace/hooks/block.h>
471 struct blk_flush_queue *blk_alloc_flush_queue(int node, int cmd_size,
472 gfp_t flags)
473 {
474 struct blk_flush_queue *fq;
475 int rq_sz = sizeof(struct request);
476 bool skip = false;
477
478 fq = kzalloc_node(sizeof(*fq), flags, node);
479 if (!fq)
480 goto fail;
481
482 spin_lock_init(&fq->mq_flush_lock);
483
> 484 trace_android_vh_blk_alloc_flush_queue(&skip, cmd_size, flags, node,
485 fq);
486 if (!skip) {
487 rq_sz = round_up(rq_sz + cmd_size, cache_line_size());
488 fq->flush_rq = kzalloc_node(rq_sz, flags, node);
489 }
490 if (!fq->flush_rq)
491 goto fail_rq;
492
493 INIT_LIST_HEAD(&fq->flush_queue[0]);
494 INIT_LIST_HEAD(&fq->flush_queue[1]);
495 INIT_LIST_HEAD(&fq->flush_data_in_flight);
496
497 lockdep_register_key(&fq->key);
498 lockdep_set_class(&fq->mq_flush_lock, &fq->key);
499
500 return fq;
501
502 fail_rq:
503 kfree(fq);
504 fail:
505 return NULL;
506 }
507
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next reply other threads:[~2024-11-24 15:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-24 15:54 kernel test robot [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-11-14 13:59 [android-common:android12-5.10 4/7] block/blk-flush.c:484:65: sparse: sparse: incorrect type in argument 3 (different base types) kernel test robot
2024-03-03 0:18 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=202411242320.mzLEc6eU-lkp@intel.com \
--to=lkp@intel.com \
--cc=cros-kernel-buildreports@googlegroups.com \
--cc=oe-kbuild-all@lists.linux.dev \
/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.