From: Chen Rong <rongx.a.chen@intel.com>
To: viro@ZenIV.linux.org.uk
Cc: lkp@intel.com, linux-fsdevel@vger.kernel.org,
adam.manzanares@wdc.com, jmoyer@redhat.com, kbuild-all@01.org,
hch@lst.de
Subject: Re: [philip.li@intel.com: Re: [kbuild-all] [vfs:work.aio 10/12] fs/aio.c:1444: undefined reference to `ioprio_check_cap']
Date: Thu, 07 Jun 2018 10:13:37 +0800 [thread overview]
Message-ID: <1528337617.3147.58.camel@intel.com> (raw)
In-Reply-To: <20180601041250.GB1251@intel.com>
Hi Viro,
I can reporduce the problem with the config (x86_64-randconfig-u0-06010558),
I guess it's because CONFIG_BLOCK is disabled in x86_64-randconfig-u0-06010558.
Thanks!
> Date: Fri, 1 Jun 2018 01:12:48 +0000
> From: "Li, Philip" <philip.li@intel.com>
> To: Al Viro <viro@ZenIV.linux.org.uk>, lkp <lkp@intel.com>
> CC: "linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>, Adam Manzanares <adam.manzanares@wdc.com>, Jeff Moyer <jmoyer@redhat.com>, "kbuild-all@01.org" <kbui
> ld-all@01.org>,
> Christoph Hellwig <hch@lst.de>
> Subject: Re: [kbuild-all] [vfs:work.aio 10/12] fs/aio.c:1444: undefined reference to `ioprio_check_cap'
>
> > On Fri, Jun 01, 2018 at 01:54:49AM +0100, Al Viro wrote:
> > > On Fri, Jun 01, 2018 at 08:36:47AM +0800, kbuild test robot wrote:
> > > > 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'
> >
> > gcc-6 ((Debian 6.3.0-18+deb9u1) 6.3.0 20170516) does not trigger that on your
> > config. Neither does gcc-5 (Debian 5.4.1-4) 5.4.1 20161202 with the same config
> > sans GCC_PLUGINS crap...
>
> thanks for input, we will double check this to check what's possibly wrong.
>
> > _______________________________________________
> > kbuild-all mailing list
> > kbuild-all@lists.01.org
> > https://lists.01.org/mailman/listinfo/kbuild-all
>
> _______________________________________________
> kbuild-all mailing list
> kbuild-all@lists.01.org
> https://lists.01.org/mailman/listinfo/kbuild-all
>
> ----- End forwarded message -----
parent reply other threads:[~2018-06-07 2:14 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20180601041250.GB1251@intel.com>]
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=1528337617.3147.58.camel@intel.com \
--to=rongx.a.chen@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=lkp@intel.com \
--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 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.