From: kernel test robot <lkp@intel.com>
To: Joanne Koong <joannelkoong@gmail.com>, axboe@kernel.dk
Cc: oe-kbuild-all@lists.linux.dev, miklos@szeredi.hu,
bschubert@ddn.com, linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH v1 7/9] fuse: add io-uring kernel-managed buffer ring
Date: Sat, 28 Mar 2026 21:27:15 +0800 [thread overview]
Message-ID: <202603282121.RW1CxOjh-lkp@intel.com> (raw)
In-Reply-To: <20260324224532.3733468-8-joannelkoong@gmail.com>
Hi Joanne,
kernel test robot noticed the following build warnings:
[auto build test WARNING on mszeredi-fuse/for-next]
[also build test WARNING on linus/master v7.0-rc5 next-20260327]
[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/Joanne-Koong/fuse-separate-next-request-fetching-from-sending-logic/20260328-142620
base: https://git.kernel.org/pub/scm/linux/kernel/git/mszeredi/fuse.git for-next
patch link: https://lore.kernel.org/r/20260324224532.3733468-8-joannelkoong%40gmail.com
patch subject: [PATCH v1 7/9] fuse: add io-uring kernel-managed buffer ring
config: powerpc64-randconfig-002-20260328 (https://download.01.org/0day-ci/archive/20260328/202603282121.RW1CxOjh-lkp@intel.com/config)
compiler: powerpc64-linux-gcc (GCC) 12.5.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260328/202603282121.RW1CxOjh-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/202603282121.RW1CxOjh-lkp@intel.com/
All warnings (new ones prefixed by >>):
In file included from fs/fuse/dev_uring.c:8:
fs/fuse/dev_uring_i.h:63:37: error: field 'payload_kvec' has incomplete type
63 | struct kvec payload_kvec;
| ^~~~~~~~~~~~
fs/fuse/dev_uring.c: In function 'fuse_uring_get_buf_ring_headers':
fs/fuse/dev_uring.c:296:24: error: implicit declaration of function 'io_uring_registered_mem_region_get' [-Werror=implicit-function-declaration]
296 | mem_reg_addr = io_uring_registered_mem_region_get(cmd, &nr_pages,
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>> fs/fuse/dev_uring.c:296:22: warning: assignment to 'void *' from 'int' makes pointer from integer without a cast [-Wint-conversion]
296 | mem_reg_addr = io_uring_registered_mem_region_get(cmd, &nr_pages,
| ^
fs/fuse/dev_uring.c: In function 'fuse_uring_buf_ring_setup':
fs/fuse/dev_uring.c:334:15: error: implicit declaration of function 'io_uring_buf_ring_pin'; did you mean 'fuse_uring_buf_ring_setup'? [-Werror=implicit-function-declaration]
334 | err = io_uring_buf_ring_pin(cmd, FUSE_URING_BUFRING_GROUP, issue_flags,
| ^~~~~~~~~~~~~~~~~~~~~
| fuse_uring_buf_ring_setup
fs/fuse/dev_uring.c:339:14: error: implicit declaration of function 'io_uring_is_kmbuf_ring' [-Werror=implicit-function-declaration]
339 | if (!io_uring_is_kmbuf_ring(cmd, FUSE_URING_BUFRING_GROUP, issue_flags))
| ^~~~~~~~~~~~~~~~~~~~~~
fs/fuse/dev_uring.c:349:9: error: implicit declaration of function 'io_uring_buf_ring_unpin'; did you mean 'fuse_uring_buf_ring_setup'? [-Werror=implicit-function-declaration]
349 | io_uring_buf_ring_unpin(cmd, FUSE_URING_BUFRING_GROUP, issue_flags);
| ^~~~~~~~~~~~~~~~~~~~~~~
| fuse_uring_buf_ring_setup
fs/fuse/dev_uring.c: In function 'fuse_uring_select_buffer':
fs/fuse/dev_uring.c:903:15: error: implicit declaration of function 'io_ring_buffer_select'; did you mean 'io_uring_cmd_buffer_select'? [-Werror=implicit-function-declaration]
903 | sel = io_ring_buffer_select(cmd_to_io_kiocb(ent->cmd), &len,
| ^~~~~~~~~~~~~~~~~~~~~
| io_uring_cmd_buffer_select
fs/fuse/dev_uring.c:903:15: error: incompatible types when assigning to type 'struct io_br_sel' from type 'int'
fs/fuse/dev_uring.c:907:18: error: 'struct io_br_sel' has no member named 'kaddr'; did you mean 'addr'?
907 | if (!sel.kaddr)
| ^~~~~
| addr
fs/fuse/dev_uring.c:910:42: error: 'struct io_br_sel' has no member named 'kaddr'; did you mean 'addr'?
910 | ent->payload_kvec.iov_base = sel.kaddr;
| ^~~~~
| addr
fs/fuse/dev_uring.c:912:27: error: 'struct io_br_sel' has no member named 'buf_id'; did you mean 'buf_list'?
912 | ent->buf_id = sel.buf_id;
| ^~~~~~
| buf_list
In file included from arch/powerpc/include/asm/bug.h:116,
from include/linux/bug.h:5,
from include/linux/instrumented.h:10,
from include/asm-generic/bitops/instrumented-atomic.h:14,
from arch/powerpc/include/asm/bitops.h:321,
from include/linux/bitops.h:67,
from include/linux/bitmap.h:8,
from include/linux/nodemask.h:91,
from include/linux/list_lru.h:12,
from include/linux/fs/super_types.h:7,
from include/linux/fs/super.h:5,
from include/linux/fs.h:5,
from fs/fuse/fuse_i.h:17,
from fs/fuse/dev_uring.c:7:
fs/fuse/dev_uring.c: In function 'fuse_uring_recycle_buffer':
fs/fuse/dev_uring.c:928:22: error: implicit declaration of function 'io_uring_kmbuf_recycle' [-Werror=implicit-function-declaration]
928 | WARN_ON_ONCE(io_uring_kmbuf_recycle(ent->cmd, FUSE_URING_BUFRING_GROUP,
| ^~~~~~~~~~~~~~~~~~~~~~
include/asm-generic/bug.h:120:32: note: in definition of macro 'WARN_ON_ONCE'
120 | int __ret_warn_on = !!(condition); \
| ^~~~~~~~~
cc1: some warnings being treated as errors
vim +296 fs/fuse/dev_uring.c
285
286 static void *fuse_uring_get_buf_ring_headers(struct io_uring_cmd *cmd,
287 u64 headers_offset,
288 unsigned int queue_depth,
289 unsigned int issue_flags)
290 {
291 void *mem_reg_addr;
292 u64 mem_reg_size, headers_size;
293 unsigned nr_pages;
294
295 /* find the headers in the registered memory region */
> 296 mem_reg_addr = io_uring_registered_mem_region_get(cmd, &nr_pages,
297 issue_flags);
298
299 /* server does not have a registered memory region set up */
300 if (!mem_reg_addr)
301 return NULL;
302
303 mem_reg_size = (u64)nr_pages * PAGE_SIZE;
304 if (headers_offset > mem_reg_size)
305 return NULL;
306
307 /* verify headers fit within memory region bounds */
308 headers_size = (u64)queue_depth * sizeof(struct fuse_uring_req_header);
309 if (mem_reg_size - headers_offset < headers_size)
310 return NULL;
311
312 return mem_reg_addr + headers_offset;
313 }
314
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2026-03-28 13:27 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-24 22:45 [PATCH v1 0/9] fuse: add io-uring buffer rings and zero-copy Joanne Koong
2026-03-24 22:45 ` [PATCH v1 1/9] fuse: separate next request fetching from sending logic Joanne Koong
2026-03-24 22:45 ` [PATCH v1 2/9] fuse: refactor io-uring header copying to ring Joanne Koong
2026-03-24 22:45 ` [PATCH v1 3/9] fuse: refactor io-uring header copying from ring Joanne Koong
2026-03-24 22:45 ` [PATCH v1 4/9] fuse: use enum types for header copying Joanne Koong
2026-03-24 22:45 ` [PATCH v1 5/9] fuse: refactor setting up copy state for payload copying Joanne Koong
2026-03-24 22:45 ` [PATCH v1 6/9] fuse: support buffer copying for kernel addresses Joanne Koong
2026-03-24 22:45 ` [PATCH v1 7/9] fuse: add io-uring kernel-managed buffer ring Joanne Koong
2026-03-28 12:21 ` kernel test robot
2026-03-28 12:54 ` kernel test robot
2026-03-28 13:27 ` kernel test robot [this message]
2026-03-30 21:28 ` Bernd Schubert
2026-03-30 23:19 ` Joanne Koong
2026-03-31 21:30 ` Bernd Schubert
2026-03-24 22:45 ` [PATCH v1 8/9] fuse: add zero-copy over io-uring Joanne Koong
2026-03-28 13:02 ` kernel test robot
2026-03-28 13:53 ` kernel test robot
2026-03-30 15:43 ` Joanne Koong
2026-03-31 3:35 ` Philip Li
2026-03-24 22:45 ` [PATCH v1 9/9] docs: fuse: add io-uring bufring and zero-copy documentation Joanne Koong
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=202603282121.RW1CxOjh-lkp@intel.com \
--to=lkp@intel.com \
--cc=axboe@kernel.dk \
--cc=bschubert@ddn.com \
--cc=joannelkoong@gmail.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=miklos@szeredi.hu \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox