From: kbuild test robot <lkp@intel.com>
To: Yangtao Li <tiny.windzz@gmail.com>
Cc: kbuild-all@01.org, john.johansen@canonical.com,
jmorris@namei.org, serge@hallyn.com,
linux-security-module@vger.kernel.org,
linux-kernel@vger.kernel.org, Yangtao Li <tiny.windzz@gmail.com>
Subject: Re: [PATCH] apparmor: Change to use DEFINE_SHOW_ATTRIBUTE macro
Date: Wed, 7 Nov 2018 09:17:21 +0800 [thread overview]
Message-ID: <201811070933.bt7EaOFh%fengguang.wu@intel.com> (raw)
In-Reply-To: <20181106143227.8287-1-tiny.windzz@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1630 bytes --]
Hi Yangtao,
Thank you for the patch! Yet something to improve:
[auto build test ERROR on security/next-testing]
[also build test ERROR on v4.20-rc1 next-20181106]
[if your patch is applied to the wrong git tree, please drop us a note to help improve the system]
url: https://github.com/0day-ci/linux/commits/Yangtao-Li/apparmor-Change-to-use-DEFINE_SHOW_ATTRIBUTE-macro/20181107-004056
base: https://git.kernel.org/pub/scm/linux/kernel/git/jmorris/linux-security.git next-testing
config: ia64-allmodconfig (attached as .config)
compiler: ia64-linux-gcc (GCC) 8.1.0
reproduce:
wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
# save the attached .config to linux build tree
GCC_VERSION=8.1.0 make.cross ARCH=ia64
All errors (new ones prefixed by >>):
>> security/apparmor/apparmorfs.o:(.data.rel+0x110): undefined reference to `aa_sfs_seq_file_ops'
security/apparmor/apparmorfs.o:(.data.rel+0x228): undefined reference to `aa_sfs_seq_file_ops'
security/apparmor/apparmorfs.o:(.data.rel+0x250): undefined reference to `aa_sfs_seq_file_ops'
security/apparmor/apparmorfs.o:(.data.rel+0x278): undefined reference to `aa_sfs_seq_file_ops'
security/apparmor/apparmorfs.o:(.data.rel+0x2c8): undefined reference to `aa_sfs_seq_file_ops'
security/apparmor/apparmorfs.o:(.data.rel+0x2f0): more undefined references to `aa_sfs_seq_file_ops' follow
---
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: 51795 bytes --]
next prev parent reply other threads:[~2018-11-07 1:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-06 14:32 Yangtao Li
2018-11-06 22:34 ` kbuild test robot
2018-11-07 1:17 ` kbuild test robot [this message]
2018-11-07 1:20 ` Frank Lee
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=201811070933.bt7EaOFh%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=jmorris@namei.org \
--cc=john.johansen@canonical.com \
--cc=kbuild-all@01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=serge@hallyn.com \
--cc=tiny.windzz@gmail.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
all inboxes | Powered by JetHome®