linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Al Viro <viro@ZenIV.linux.org.uk>
To: kbuild test robot <lkp@intel.com>
Cc: Adam Manzanares <adam.manzanares@wdc.com>,
	kbuild-all@01.org, linux-fsdevel@vger.kernel.org,
	Jeff Moyer <jmoyer@redhat.com>, Christoph Hellwig <hch@lst.de>
Subject: Re: [vfs:work.aio 10/12] fs/aio.c:1444: undefined reference to `ioprio_check_cap'
Date: Fri, 1 Jun 2018 02:02:47 +0100	[thread overview]
Message-ID: <20180601010246.GO30522@ZenIV.linux.org.uk> (raw)
In-Reply-To: <20180601005448.GN30522@ZenIV.linux.org.uk>

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...

  reply	other threads:[~2018-06-01  1:02 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-01  0:36 [vfs:work.aio 10/12] fs/aio.c:1444: undefined reference to `ioprio_check_cap' kbuild test robot
2018-06-01  0:54 ` Al Viro
2018-06-01  1:02   ` Al Viro [this message]
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=20180601010246.GO30522@ZenIV.linux.org.uk \
    --to=viro@zeniv.linux.org.uk \
    --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 \
    /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).