From: kernel test robot <lkp@intel.com>
To: David Howells <dhowells@redhat.com>
Cc: oe-kbuild-all@lists.linux.dev
Subject: [dhowells-fs:netfs-fixes 1/2] fs/erofs/fscache.c:122:20: error: assignment to 'netfs_io_terminated_t' {aka 'void (*)(void *, int)'} from incompatible pointer type 'void (*)(void *, ssize_t, bool)' {aka 'void (*)(void *, int, _Bool)'}
Date: Thu, 20 Feb 2025 05:37:33 +0800 [thread overview]
Message-ID: <202502200514.AOFaBjkD-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/dhowells/linux-fs.git netfs-fixes
head: 423353c292d881a53125bbe8aff5fcc329f3dbb7
commit: c313ce74e3946fcc6ae5c80187c8d576ac097a65 [1/2] netfs: Fix the request's work item to not require a ref
config: arm-randconfig-004-20250220 (https://download.01.org/0day-ci/archive/20250220/202502200514.AOFaBjkD-lkp@intel.com/config)
compiler: arm-linux-gnueabi-gcc (GCC) 14.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250220/202502200514.AOFaBjkD-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/202502200514.AOFaBjkD-lkp@intel.com/
All errors (new ones prefixed by >>):
fs/erofs/fscache.c: In function 'erofs_fscache_req_io_alloc':
>> fs/erofs/fscache.c:122:20: error: assignment to 'netfs_io_terminated_t' {aka 'void (*)(void *, int)'} from incompatible pointer type 'void (*)(void *, ssize_t, bool)' {aka 'void (*)(void *, int, _Bool)'} [-Wincompatible-pointer-types]
122 | io->end_io = erofs_fscache_req_end_io;
| ^
fs/erofs/fscache.c: In function 'erofs_fscache_bio_alloc':
fs/erofs/fscache.c:202:23: error: assignment to 'netfs_io_terminated_t' {aka 'void (*)(void *, int)'} from incompatible pointer type 'void (*)(void *, ssize_t, bool)' {aka 'void (*)(void *, int, _Bool)'} [-Wincompatible-pointer-types]
202 | io->io.end_io = erofs_fscache_bio_endio;
| ^
vim +122 fs/erofs/fscache.c
f2151df5743536 Jingbo Xu 2024-03-08 115
f2151df5743536 Jingbo Xu 2024-03-08 116 static struct erofs_fscache_io *erofs_fscache_req_io_alloc(struct erofs_fscache_rq *req)
f2151df5743536 Jingbo Xu 2024-03-08 117 {
f2151df5743536 Jingbo Xu 2024-03-08 118 struct erofs_fscache_io *io = kzalloc(sizeof(*io), GFP_KERNEL);
f2151df5743536 Jingbo Xu 2024-03-08 119
f2151df5743536 Jingbo Xu 2024-03-08 120 if (!io)
f2151df5743536 Jingbo Xu 2024-03-08 121 return NULL;
f2151df5743536 Jingbo Xu 2024-03-08 @122 io->end_io = erofs_fscache_req_end_io;
f2151df5743536 Jingbo Xu 2024-03-08 123 io->private = req;
f2151df5743536 Jingbo Xu 2024-03-08 124 refcount_inc(&req->ref);
f2151df5743536 Jingbo Xu 2024-03-08 125 refcount_set(&io->ref, 1);
f2151df5743536 Jingbo Xu 2024-03-08 126 return io;
d435d53228dd03 Xin Yin 2022-05-09 127 }
d435d53228dd03 Xin Yin 2022-05-09 128
:::::: The code at line 122 was first introduced by commit
:::::: f2151df5743536e0b98a2094bd58b52d4e060016 erofs: make iov_iter describe target buffers over fscache
:::::: TO: Jingbo Xu <jefflexu@linux.alibaba.com>
:::::: CC: Gao Xiang <hsiangkao@linux.alibaba.com>
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2025-02-19 21:39 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=202502200514.AOFaBjkD-lkp@intel.com \
--to=lkp@intel.com \
--cc=dhowells@redhat.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.