From: kernel test robot <lkp@intel.com>
To: oe-kbuild@lists.linux.dev
Cc: lkp@intel.com, Julia Lawall <julia.lawall@inria.fr>
Subject: Re: [PATCH V10 12/12] ublk: support leasing io buffer to io_uring
Date: Fri, 8 Nov 2024 06:15:45 +0800 [thread overview]
Message-ID: <202411080639.shF21Vmc-lkp@intel.com> (raw)
BCC: lkp@intel.com
CC: oe-kbuild-all@lists.linux.dev
In-Reply-To: <20241107110149.890530-13-ming.lei@redhat.com>
References: <20241107110149.890530-13-ming.lei@redhat.com>
TO: Ming Lei <ming.lei@redhat.com>
TO: Jens Axboe <axboe@kernel.dk>
TO: io-uring@vger.kernel.org
TO: Pavel Begunkov <asml.silence@gmail.com>
CC: linux-block@vger.kernel.org
CC: Uday Shankar <ushankar@purestorage.com>
CC: Akilesh Kailash <akailash@google.com>
CC: Ming Lei <ming.lei@redhat.com>
Hi Ming,
kernel test robot noticed the following build warnings:
[auto build test WARNING on axboe-block/for-next]
[also build test WARNING on next-20241107]
[cannot apply to linus/master v6.12-rc6]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch#_base_tree_information]
url: https://github.com/intel-lab-lkp/linux/commits/Ming-Lei/io_uring-rsrc-pass-struct-io_ring_ctx-reference-to-rsrc-helpers/20241107-190456
base: https://git.kernel.org/pub/scm/linux/kernel/git/axboe/linux-block.git for-next
patch link: https://lore.kernel.org/r/20241107110149.890530-13-ming.lei%40redhat.com
patch subject: [PATCH V10 12/12] ublk: support leasing io buffer to io_uring
:::::: branch date: 11 hours ago
:::::: commit date: 11 hours ago
config: x86_64-randconfig-r063-20241108 (https://download.01.org/0day-ci/archive/20241108/202411080639.shF21Vmc-lkp@intel.com/config)
compiler: gcc-12 (Debian 12.2.0-14) 12.2.0
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>
| Reported-by: Julia Lawall <julia.lawall@inria.fr>
| Closes: https://lore.kernel.org/r/202411080639.shF21Vmc-lkp@intel.com/
cocci warnings: (new ones prefixed by >>)
>> drivers/block/ublk_drv.c:88:19-22: WARNING use flexible-array member instead (https://www.kernel.org/doc/html/latest/process/deprecated.html#zero-length-and-one-element-arrays)
vim +88 drivers/block/ublk_drv.c
79e9f68a5502d0 Ming Lei 2024-11-07 81
0edb3696c1713c Ming Lei 2022-07-13 82 struct ublk_rq_data {
3ab6e94ca53924 Ming Lei 2022-10-29 83 struct llist_node node;
8284066946e6d9 Ming Lei 2023-05-19 84
8284066946e6d9 Ming Lei 2023-05-19 85 struct kref ref;
79e9f68a5502d0 Ming Lei 2024-11-07 86
79e9f68a5502d0 Ming Lei 2024-11-07 87 bool allocated_bvec;
79e9f68a5502d0 Ming Lei 2024-11-07 @88 struct uring_kbuf buf[0];
0edb3696c1713c Ming Lei 2022-07-13 89 };
0edb3696c1713c Ming Lei 2022-07-13 90
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next reply other threads:[~2024-11-07 22:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-07 22:15 kernel test robot [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-11-07 11:01 [PATCH V10 0/12] io_uring: support group buffer & ublk zc Ming Lei
2024-11-07 11:01 ` [PATCH V10 12/12] ublk: support leasing io buffer to io_uring Ming Lei
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=202411080639.shF21Vmc-lkp@intel.com \
--to=lkp@intel.com \
--cc=julia.lawall@inria.fr \
--cc=oe-kbuild@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.