From: Jens Axboe <axboe@kernel.dk>
To: kernel test robot <lkp@intel.com>
Cc: Max Kellermann <max.kellermann@ionos.com>, oe-kbuild-all@lists.linux.dev
Subject: Re: [axboe-block:io_uring-epoll-wait 7/19] io_uring/io_uring.c:396:43: sparse: sparse: incorrect type in initializer (different base types)
Date: Sun, 2 Feb 2025 08:03:50 -0700 [thread overview]
Message-ID: <ad76426d-7d2e-45c5-ab19-a6b9679b0b2f@kernel.dk> (raw)
In-Reply-To: <202502021802.ulY6VEco-lkp@intel.com>
On Sun, Feb 2, 2025 at 3:19?AM kernel test robot <lkp@intel.com> wrote:
>
> tree: https://git.kernel.org/pub/scm/linux/kernel/git/axboe/linux-block.git io_uring-epoll-wait
> head: 81a642b29d7d837fda2d86c4e1dc036effcfa4a7
> commit: 4fbd68dbbb65f14f3fd40e1232045e06d168ecbd [7/19] io_uring: cache io_kiocb->flags in variable
> config: hexagon-randconfig-r112-20250202 (https://download.01.org/0day-ci/archive/20250202/202502021802.ulY6VEco-lkp@intel.com/config)
> compiler: clang version 21.0.0git (https://github.com/llvm/llvm-project 355d0b186f178668b103068537e517f3d52ad639)
> reproduce: (https://download.01.org/0day-ci/archive/20250202/202502021802.ulY6VEco-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/202502021802.ulY6VEco-lkp@intel.com/
>
> sparse warnings: (new ones prefixed by >>)
> io_uring/io_uring.c: note: in included file (through include/linux/io_uring/cmd.h):
> include/linux/io_uring_types.h:191:37: sparse: sparse: array of flexible structures
> >> io_uring/io_uring.c:396:43: sparse: sparse: incorrect type in initializer (different base types) @@ expected unsigned int const req_flags @@ got restricted io_req_flags_t [usertype] flags @@
> io_uring/io_uring.c:396:43: sparse: expected unsigned int const req_flags
> io_uring/io_uring.c:396:43: sparse: got restricted io_req_flags_t [usertype] flags
> >> io_uring/io_uring.c:398:25: sparse: sparse: restricted io_req_flags_t degrades to integer
I've folded in a patch making it io_req_flags_t, which is the correct
type. Missed that...
--
Jens Axboe
prev parent reply other threads:[~2025-02-02 15:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-02 10:19 [axboe-block:io_uring-epoll-wait 7/19] io_uring/io_uring.c:396:43: sparse: sparse: incorrect type in initializer (different base types) kernel test robot
2025-02-02 15:03 ` Jens Axboe [this message]
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=ad76426d-7d2e-45c5-ab19-a6b9679b0b2f@kernel.dk \
--to=axboe@kernel.dk \
--cc=lkp@intel.com \
--cc=max.kellermann@ionos.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.