From: kbuild test robot <lkp@intel.com>
To: Adam Manzanares <adam.manzanares@wdc.com>
Cc: kbuild-all@01.org, linux-fsdevel@vger.kernel.org,
Al Viro <viro@zeniv.linux.org.uk>, Jeff Moyer <jmoyer@redhat.com>,
Christoph Hellwig <hch@lst.de>
Subject: [vfs:work.aio 10/12] fs/aio.c:1444: undefined reference to `ioprio_check_cap'
Date: Fri, 1 Jun 2018 08:36:47 +0800 [thread overview]
Message-ID: <201806010845.bDzP7QCW%fengguang.wu@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2001 bytes --]
tree: https://git.kernel.org/pub/scm/linux/kernel/git/viro/vfs.git work.aio
head: 087e566916ce2cde4f20a148607c9c3591f46f67
commit: d9a08a9e616beeccdbd0e7262b7225ffdfa49e92 [10/12] fs: Add aio iopriority support
config: x86_64-randconfig-u0-06010558 (attached as .config)
compiler: gcc-5 (Debian 5.5.0-3) 5.4.1 20171010
reproduce:
git checkout d9a08a9e616beeccdbd0e7262b7225ffdfa49e92
# save the attached .config to linux build tree
make ARCH=x86_64
All errors (new ones prefixed by >>):
fs/aio.o: In function `aio_prep_rw':
>> fs/aio.c:1444: undefined reference to `ioprio_check_cap'
vim +1444 fs/aio.c
1424
1425 static int aio_prep_rw(struct kiocb *req, struct iocb *iocb)
1426 {
1427 int ret;
1428
1429 req->ki_filp = fget(iocb->aio_fildes);
1430 if (unlikely(!req->ki_filp))
1431 return -EBADF;
1432 req->ki_complete = aio_complete_rw;
1433 req->ki_pos = iocb->aio_offset;
1434 req->ki_flags = iocb_flags(req->ki_filp);
1435 if (iocb->aio_flags & IOCB_FLAG_RESFD)
1436 req->ki_flags |= IOCB_EVENTFD;
1437 req->ki_hint = ki_hint_validate(file_write_hint(req->ki_filp));
1438 if (iocb->aio_flags & IOCB_FLAG_IOPRIO) {
1439 /*
1440 * If the IOCB_FLAG_IOPRIO flag of aio_flags is set, then
1441 * aio_reqprio is interpreted as an I/O scheduling
1442 * class and priority.
1443 */
> 1444 ret = ioprio_check_cap(iocb->aio_reqprio);
1445 if (ret) {
1446 pr_debug("aio ioprio check cap error\n");
1447 return -EINVAL;
1448 }
1449
1450 req->ki_ioprio = iocb->aio_reqprio;
1451 } else
1452 req->ki_ioprio = IOPRIO_PRIO_VALUE(IOPRIO_CLASS_NONE, 0);
1453
1454 ret = kiocb_set_rw_flags(req, iocb->aio_rw_flags);
1455 if (unlikely(ret))
1456 fput(req->ki_filp);
1457 return ret;
1458 }
1459
---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all Intel Corporation
[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 29644 bytes --]
next reply other threads:[~2018-06-01 0:37 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-01 0:36 kbuild test robot [this message]
2018-06-01 0:54 ` [vfs:work.aio 10/12] fs/aio.c:1444: undefined reference to `ioprio_check_cap' Al Viro
2018-06-01 1:02 ` Al Viro
2018-06-01 1:12 ` [kbuild-all] " Li, Philip
2018-06-01 5:13 ` Christoph Hellwig
2018-06-01 15:38 ` Adam Manzanares
2018-06-01 15:41 ` Jens Axboe
2018-06-01 15:57 ` Adam Manzanares
2018-06-01 15:59 ` Jens Axboe
2018-06-01 17:28 ` Matthew Wilcox
2018-06-01 20:31 ` Steve French
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=201806010845.bDzP7QCW%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=adam.manzanares@wdc.com \
--cc=hch@lst.de \
--cc=jmoyer@redhat.com \
--cc=kbuild-all@01.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=viro@zeniv.linux.org.uk \
/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;
as well as URLs for NNTP newsgroup(s).