From: Al Viro <viro@ZenIV.linux.org.uk>
To: kbuild test robot <lkp@intel.com>
Cc: David Howells <dhowells@redhat.com>,
kbuild-all@01.org, linux-fsdevel@vger.kernel.org
Subject: Re: [vfs:mount-open_tree 47/55] (.text.__se_sys_fsopen+0xb4): undefined reference to `anon_inode_getfd'
Date: Sun, 3 Jun 2018 04:26:58 +0100 [thread overview]
Message-ID: <20180603032649.GA30522@ZenIV.linux.org.uk> (raw)
In-Reply-To: <201806031122.Nv7XdyqU%fengguang.wu@intel.com>
On Sun, Jun 03, 2018 at 11:14:26AM +0800, kbuild test robot wrote:
> tree: https://git.kernel.org/pub/scm/linux/kernel/git/viro/vfs.git mount-open_tree
> head: 9f567b215a24571545746d762321e8dd13150108
> commit: 644ed0fc203837691e612cd0792a668079518382 [47/55] VFS: Implement fsopen() to prepare for a mount
> config: parisc-allnoconfig (attached as .config)
> compiler: hppa-linux-gnu-gcc (Debian 7.2.0-11) 7.2.0
> reproduce:
> wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
> chmod +x ~/bin/make.cross
> git checkout 644ed0fc203837691e612cd0792a668079518382
> # save the attached .config to linux build tree
> make.cross ARCH=parisc
>
> All errors (new ones prefixed by >>):
>
> fs/fsopen.o: In function `__se_sys_fsopen':
> >> (.text.__se_sys_fsopen+0xb4): undefined reference to `anon_inode_getfd'
Why, in name of everything unholy, does CONFIG_ANON_INODES exist, in the first
place? Should be unconditional, IMO.
prev parent reply other threads:[~2018-06-03 3:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-03 3:14 [vfs:mount-open_tree 47/55] (.text.__se_sys_fsopen+0xb4): undefined reference to `anon_inode_getfd' kbuild test robot
2018-06-03 3:26 ` Al Viro [this message]
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=20180603032649.GA30522@ZenIV.linux.org.uk \
--to=viro@zeniv.linux.org.uk \
--cc=dhowells@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 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.