From: kbuild test robot <lkp@intel.com>
To: Richard Guy Briggs <rgb@redhat.com>,
Linux-Audit Mailing List <linux-audit@redhat.com>,
LKML <linux-kernel@vger.kernel.org>,
netfilter-devel@vger.kernel.org
Cc: kbuild-all@lists.01.org, fw@strlen.de, twoerner@redhat.com,
eparis@parisplace.org, tgraf@infradead.org
Subject: Re: [PATCH ghak124 v2] audit: log nftables configuration change events
Date: Mon, 1 Jun 2020 07:38:07 +0800 [thread overview]
Message-ID: <202006010711.XsbeqYjc%lkp@intel.com> (raw)
In-Reply-To: <d45d23ba6d58b1513c641dfb24f009cbc1b7aad6.1590716354.git.rgb@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 3343 bytes --]
Hi Richard,
Thank you for the patch! Yet something to improve:
[auto build test ERROR on pcmoore-audit/next]
[also build test ERROR on next-20200529]
[cannot apply to nf/master nf-next/master linus/master linux/master v5.7-rc7]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system. BTW, we also suggest to use '--base' option to specify the
base tree in git format-patch, please see https://stackoverflow.com/a/37406982]
url: https://github.com/0day-ci/linux/commits/Richard-Guy-Briggs/audit-log-nftables-configuration-change-events/20200531-043244
base: https://git.kernel.org/pub/scm/linux/kernel/git/pcmoore/audit.git next
config: sparc-allyesconfig (attached as .config)
compiler: sparc64-linux-gcc (GCC) 9.3.0
reproduce (this is a W=1 build):
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
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-9.3.0 make.cross ARCH=sparc
If you fix the issue, kindly add following tag as appropriate
Reported-by: kbuild test robot <lkp@intel.com>
All errors (new ones prefixed by >>, old ones prefixed by <<):
In file included from arch/sparc/kernel/ptrace_64.c:25:
>> include/linux/audit.h:126:40: error: 'audit_nftcfgs' defined but not used [-Werror=unused-const-variable=]
126 | static const struct audit_nftcfgop_tab audit_nftcfgs[] = {
| ^~~~~~~~~~~~~
cc1: all warnings being treated as errors
vim +/audit_nftcfgs +126 include/linux/audit.h
125
> 126 static const struct audit_nftcfgop_tab audit_nftcfgs[] = {
127 { NFT_MSG_NEWTABLE, AUDIT_NFT_OP_TABLE_REGISTER },
128 { NFT_MSG_GETTABLE, AUDIT_NFT_OP_INVALID },
129 { NFT_MSG_DELTABLE, AUDIT_NFT_OP_TABLE_UNREGISTER },
130 { NFT_MSG_NEWCHAIN, AUDIT_NFT_OP_CHAIN_REGISTER },
131 { NFT_MSG_GETCHAIN, AUDIT_NFT_OP_INVALID },
132 { NFT_MSG_DELCHAIN, AUDIT_NFT_OP_CHAIN_UNREGISTER },
133 { NFT_MSG_NEWRULE, AUDIT_NFT_OP_RULE_REGISTER },
134 { NFT_MSG_GETRULE, AUDIT_NFT_OP_INVALID },
135 { NFT_MSG_DELRULE, AUDIT_NFT_OP_RULE_UNREGISTER },
136 { NFT_MSG_NEWSET, AUDIT_NFT_OP_SET_REGISTER },
137 { NFT_MSG_GETSET, AUDIT_NFT_OP_INVALID },
138 { NFT_MSG_DELSET, AUDIT_NFT_OP_SET_UNREGISTER },
139 { NFT_MSG_NEWSETELEM, AUDIT_NFT_OP_SETELEM_REGISTER },
140 { NFT_MSG_GETSETELEM, AUDIT_NFT_OP_INVALID },
141 { NFT_MSG_DELSETELEM, AUDIT_NFT_OP_SETELEM_UNREGISTER },
142 { NFT_MSG_NEWGEN, AUDIT_NFT_OP_GEN_REGISTER },
143 { NFT_MSG_GETGEN, AUDIT_NFT_OP_INVALID },
144 { NFT_MSG_TRACE, AUDIT_NFT_OP_INVALID },
145 { NFT_MSG_NEWOBJ, AUDIT_NFT_OP_OBJ_REGISTER },
146 { NFT_MSG_GETOBJ, AUDIT_NFT_OP_INVALID },
147 { NFT_MSG_DELOBJ, AUDIT_NFT_OP_OBJ_UNREGISTER },
148 { NFT_MSG_GETOBJ_RESET, AUDIT_NFT_OP_OBJ_RESET },
149 { NFT_MSG_NEWFLOWTABLE, AUDIT_NFT_OP_FLOWTABLE_REGISTER },
150 { NFT_MSG_GETFLOWTABLE, AUDIT_NFT_OP_INVALID },
151 { NFT_MSG_DELFLOWTABLE, AUDIT_NFT_OP_FLOWTABLE_UNREGISTER },
152 { NFT_MSG_MAX, AUDIT_NFT_OP_INVALID },
153 };
154
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 62442 bytes --]
[-- Attachment #3: Type: text/plain, Size: 102 bytes --]
--
Linux-audit mailing list
Linux-audit@redhat.com
https://www.redhat.com/mailman/listinfo/linux-audit
next prev parent reply other threads:[~2020-06-01 13:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-29 1:44 [PATCH ghak124 v2] audit: log nftables configuration change events Richard Guy Briggs
2020-05-31 23:38 ` kbuild test robot [this message]
2020-06-01 16:10 ` Paul Moore
2020-06-01 22:58 ` Richard Guy Briggs
2020-06-02 0:12 ` Paul Moore
2020-06-02 11:34 ` Richard Guy Briggs
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=202006010711.XsbeqYjc%lkp@intel.com \
--to=lkp@intel.com \
--cc=eparis@parisplace.org \
--cc=fw@strlen.de \
--cc=kbuild-all@lists.01.org \
--cc=linux-audit@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netfilter-devel@vger.kernel.org \
--cc=rgb@redhat.com \
--cc=tgraf@infradead.org \
--cc=twoerner@redhat.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