From: kbuild test robot <fengguang.wu@intel.com>
To: Tyler Hicks <tyhicks@canonical.com>
Cc: kbuild-all@01.org, ecryptfs@vger.kernel.org
Subject: [ecryptfs:seccomp-logging 2/5] include/linux/audit.h:528:20: warning: '__audit_seccomp' declared 'static' but never defined
Date: Sun, 8 Jan 2017 06:54:24 +0800 [thread overview]
Message-ID: <201701080621.uOFzBJWr%fengguang.wu@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2796 bytes --]
tree: https://git.kernel.org/pub/scm/linux/kernel/git/tyhicks/ecryptfs.git seccomp-logging
head: cb693c3bd88cb403e9a72ef8d3e8647af90ddd1c
commit: 22f461512135136047a2bcaf5edb179fb3523bc0 [2/5] seccomp: Audit SECCOMP_RET_ERRNO actions with errno values
config: tile-allmodconfig (attached as .config)
compiler: tilegx-linux-gcc (GCC) 4.6.2
reproduce:
wget https://git.kernel.org/cgit/linux/kernel/git/wfg/lkp-tests.git/plain/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
git checkout 22f461512135136047a2bcaf5edb179fb3523bc0
# save the attached .config to linux build tree
make.cross ARCH=tile
All warnings (new ones prefixed by >>):
In file included from kernel/fork.c:50:0:
include/linux/audit.h:530:1: error: expected identifier or '(' before '{' token
>> include/linux/audit.h:528:20: warning: '__audit_seccomp' declared 'static' but never defined [-Wunused-function]
--
In file included from kernel/seccomp.c:17:0:
include/linux/audit.h:530:1: error: expected identifier or '(' before '{' token
kernel/seccomp.c: In function '__seccomp_filter':
kernel/seccomp.c:580:3: error: implicit declaration of function 'audit_seccomp_errno'
kernel/seccomp.c: At top level:
>> include/linux/audit.h:528:20: warning: '__audit_seccomp' declared 'static' but never defined
cc1: some warnings being treated as errors
vim +528 include/linux/audit.h
d6335d77 Andreas Gruenbacher 2015-12-24 522 static inline void audit_inode_child(struct inode *parent,
4fa6b5ec Jeff Layton 2012-10-10 523 const struct dentry *dentry,
4fa6b5ec Jeff Layton 2012-10-10 524 const unsigned char type)
9321d526 Kees Cook 2012-10-04 525 { }
9321d526 Kees Cook 2012-10-04 526 static inline void audit_core_dumps(long signr)
9321d526 Kees Cook 2012-10-04 527 { }
28bedd6a Tyler Hicks 2016-12-01 @528 static inline void __audit_seccomp(unsigned long syscall,
28bedd6a Tyler Hicks 2016-12-01 529 struct audit_seccomp_info *info);
28bedd6a Tyler Hicks 2016-12-01 @530 { }
28bedd6a Tyler Hicks 2016-12-01 531 static inline void audit_seccomp_signal(unsigned long syscall, long signr,
28bedd6a Tyler Hicks 2016-12-01 532 int code)
9321d526 Kees Cook 2012-10-04 533 { }
:::::: The code at line 528 was first introduced by commit
:::::: 28bedd6ad6bf644620d0690d9025b801f2a706cc seccomp: Allow for auditing functionality specific to return actions
:::::: TO: Tyler Hicks <tyhicks@canonical.com>
:::::: CC: Tyler Hicks <tyhicks@canonical.com>
---
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: 47087 bytes --]
reply other threads:[~2017-01-07 22:55 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=201701080621.uOFzBJWr%fengguang.wu@intel.com \
--to=fengguang.wu@intel.com \
--cc=ecryptfs@vger.kernel.org \
--cc=kbuild-all@01.org \
--cc=tyhicks@canonical.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 read-only IMAP folder(s) and NNTP newsgroup(s).