From: kernel test robot <lkp@intel.com>
To: Stefan Roesch <shr@fb.com>
Cc: kbuild-all@lists.01.org,
Linux Memory Management List <linux-mm@kvack.org>,
Jens Axboe <axboe@kernel.dk>
Subject: [linux-next:master 7511/8646] fs/io_uring.c:4768:30: error: passing argument 2 of 'do_statx' from incompatible pointer type
Date: Fri, 25 Feb 2022 17:04:09 +0800 [thread overview]
Message-ID: <202202251631.mnGl4XST-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
head: 44948bd49d878dad6c9707e34f4a06df73c3a800
commit: 30512d54fae354a2359a740b75a1451b68aa3807 [7511/8646] fs: replace const char* parameter in vfs_statx and do_statx with struct filename
config: x86_64-rhel-8.3-func (https://download.01.org/0day-ci/archive/20220225/202202251631.mnGl4XST-lkp@intel.com/config)
compiler: gcc-9 (Debian 9.3.0-22) 9.3.0
reproduce (this is a W=1 build):
# https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?id=30512d54fae354a2359a740b75a1451b68aa3807
git remote add linux-next https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
git fetch --no-tags linux-next master
git checkout 30512d54fae354a2359a740b75a1451b68aa3807
# save the config file to linux build tree
mkdir build_dir
make W=1 O=build_dir ARCH=x86_64 SHELL=/bin/bash
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>
Note: the linux-next/master HEAD 44948bd49d878dad6c9707e34f4a06df73c3a800 builds fine.
It may have been fixed somewhere.
All errors (new ones prefixed by >>):
fs/io_uring.c: In function '__io_submit_flush_completions':
fs/io_uring.c:2544:33: warning: variable 'prev' set but not used [-Wunused-but-set-variable]
2544 | struct io_wq_work_node *node, *prev;
| ^~~~
fs/io_uring.c: In function 'io_statx':
>> fs/io_uring.c:4768:30: error: passing argument 2 of 'do_statx' from incompatible pointer type [-Werror=incompatible-pointer-types]
4768 | ret = do_statx(ctx->dfd, ctx->filename, ctx->flags, ctx->mask,
| ~~~^~~~~~~~~~
| |
| const char *
In file included from fs/io_uring.c:90:
fs/internal.h:189:40: note: expected 'struct filename *' but argument is of type 'const char *'
189 | int do_statx(int dfd, struct filename *filename, unsigned int flags,
| ~~~~~~~~~~~~~~~~~^~~~~~~~
cc1: some warnings being treated as errors
vim +/do_statx +4768 fs/io_uring.c
eddc7ef52a6b37 Jens Axboe 2019-12-13 4759
45d189c6062922 Pavel Begunkov 2021-02-10 4760 static int io_statx(struct io_kiocb *req, unsigned int issue_flags)
eddc7ef52a6b37 Jens Axboe 2019-12-13 4761 {
1d9e1288039a47 Bijan Mottahedeh 2020-05-22 4762 struct io_statx *ctx = &req->statx;
eddc7ef52a6b37 Jens Axboe 2019-12-13 4763 int ret;
eddc7ef52a6b37 Jens Axboe 2019-12-13 4764
59d7001345a7b9 Pavel Begunkov 2021-03-22 4765 if (issue_flags & IO_URING_F_NONBLOCK)
eddc7ef52a6b37 Jens Axboe 2019-12-13 4766 return -EAGAIN;
eddc7ef52a6b37 Jens Axboe 2019-12-13 4767
e62753e4e2926f Bijan Mottahedeh 2020-05-22 @4768 ret = do_statx(ctx->dfd, ctx->filename, ctx->flags, ctx->mask,
e62753e4e2926f Bijan Mottahedeh 2020-05-22 4769 ctx->buffer);
eddc7ef52a6b37 Jens Axboe 2019-12-13 4770
eddc7ef52a6b37 Jens Axboe 2019-12-13 4771 if (ret < 0)
93d2bcd2cbfed2 Pavel Begunkov 2021-05-16 4772 req_set_fail(req);
e1e16097e265da Jens Axboe 2020-06-22 4773 io_req_complete(req, ret);
eddc7ef52a6b37 Jens Axboe 2019-12-13 4774 return 0;
eddc7ef52a6b37 Jens Axboe 2019-12-13 4775 }
eddc7ef52a6b37 Jens Axboe 2019-12-13 4776
:::::: The code at line 4768 was first introduced by commit
:::::: e62753e4e2926f249d088cc0517be5ed4efec6d6 io_uring: call statx directly
:::::: TO: Bijan Mottahedeh <bijan.mottahedeh@oracle.com>
:::::: CC: Jens Axboe <axboe@kernel.dk>
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
reply other threads:[~2022-02-25 9:05 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=202202251631.mnGl4XST-lkp@intel.com \
--to=lkp@intel.com \
--cc=axboe@kernel.dk \
--cc=kbuild-all@lists.01.org \
--cc=linux-mm@kvack.org \
--cc=shr@fb.com \
/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