From: kbuild test robot <lkp@intel.com>
To: kbuild-all@lists.01.org
Subject: [block:for-5.6/io_uring 45/45] fs/io_uring.c:2475: undefined reference to `do_madvise'
Date: Thu, 26 Dec 2019 17:03:51 +0800 [thread overview]
Message-ID: <201912261750.7X4yte4T%lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1448 bytes --]
tree: https://git.kernel.org/pub/scm/linux/kernel/git/axboe/linux-block.git for-5.6/io_uring
head: fd4be9bbc3f977f9e89056b93e0c6b1249a0ae0f
commit: fd4be9bbc3f977f9e89056b93e0c6b1249a0ae0f [45/45] io_uring: add IORING_OP_MADVISE
config: x86_64-randconfig-b001-20191225 (attached as .config)
compiler: gcc-7 (Debian 7.5.0-3) 7.5.0
reproduce:
git checkout fd4be9bbc3f977f9e89056b93e0c6b1249a0ae0f
# save the attached .config to linux build tree
make ARCH=x86_64
If you fix the issue, kindly add following tag
Reported-by: kbuild test robot <lkp@intel.com>
All errors (new ones prefixed by >>):
ld: fs/io_uring.o: in function `io_madvise':
>> fs/io_uring.c:2475: undefined reference to `do_madvise'
vim +2475 fs/io_uring.c
2465
2466 static int io_madvise(struct io_kiocb *req, struct io_kiocb **nxt,
2467 bool force_nonblock)
2468 {
2469 struct io_fadvise *fa = &req->fadvise;
2470 int ret;
2471
2472 if (force_nonblock)
2473 return -EAGAIN;
2474
> 2475 ret = do_madvise(fa->addr, fa->len, fa->advice);
2476 if (ret < 0)
2477 req_set_fail_links(req);
2478 io_cqring_add_event(req, ret);
2479 io_put_req_find_next(req, nxt);
2480 return 0;
2481 }
2482
---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org Intel Corporation
[-- Attachment #2: config.gz --]
[-- Type: application/gzip, Size: 30716 bytes --]
reply other threads:[~2019-12-26 9:03 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=201912261750.7X4yte4T%lkp@intel.com \
--to=lkp@intel.com \
--cc=kbuild-all@lists.01.org \
/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.