From: kbuild test robot <lkp@intel.com>
To: Johannes Berg <johannes.berg@intel.com>
Cc: kbuild-all@01.org, linux-wireless@vger.kernel.org
Subject: [mac80211-next:netlink-validate-build-test-2 2/6] net/sched/act_tunnel_key.c:128:8: error: implicit declaration of function 'nla_validate_deprecated'
Date: Mon, 25 Mar 2019 23:01:42 +0800 [thread overview]
Message-ID: <201903252340.RGqudbwk%lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2379 bytes --]
tree: https://git.kernel.org/pub/scm/linux/kernel/git/jberg/mac80211-next.git netlink-validate-build-test-2
head: 963dafe164a051f6763a6fddf7b6d7933076985c
commit: e2e82c1203c1ab2423a79f486567a49228f546ab [2/6] netlink: make validation more configurable for future strictness
config: x86_64-randconfig-l3-03250457 (attached as .config)
compiler: gcc-5 (Debian 5.5.0-3) 5.4.1 20171010
reproduce:
git checkout e2e82c1203c1ab2423a79f486567a49228f546ab
# save the attached .config to linux build tree
make ARCH=x86_64
All errors (new ones prefixed by >>):
net/sched/act_tunnel_key.c: In function 'tunnel_key_copy_opts':
>> net/sched/act_tunnel_key.c:128:8: error: implicit declaration of function 'nla_validate_deprecated' [-Werror=implicit-function-declaration]
err = nla_validate_deprecated(head, len, TCA_TUNNEL_KEY_ENC_OPTS_MAX,
^
cc1: some warnings being treated as errors
vim +/nla_validate_deprecated +128 net/sched/act_tunnel_key.c
121
122 static int tunnel_key_copy_opts(const struct nlattr *nla, u8 *dst,
123 int dst_len, struct netlink_ext_ack *extack)
124 {
125 int err, rem, opt_len, len = nla_len(nla), opts_len = 0;
126 const struct nlattr *attr, *head = nla_data(nla);
127
> 128 err = nla_validate_deprecated(head, len, TCA_TUNNEL_KEY_ENC_OPTS_MAX,
129 enc_opts_policy, extack);
130 if (err)
131 return err;
132
133 nla_for_each_attr(attr, head, len, rem) {
134 switch (nla_type(attr)) {
135 case TCA_TUNNEL_KEY_ENC_OPTS_GENEVE:
136 opt_len = tunnel_key_copy_geneve_opt(attr, dst,
137 dst_len, extack);
138 if (opt_len < 0)
139 return opt_len;
140 opts_len += opt_len;
141 if (dst) {
142 dst_len -= opt_len;
143 dst += opt_len;
144 }
145 break;
146 }
147 }
148
149 if (!opts_len) {
150 NL_SET_ERR_MSG(extack, "Empty list of tunnel options");
151 return -EINVAL;
152 }
153
154 if (rem > 0) {
155 NL_SET_ERR_MSG(extack, "Trailing data after parsing tunnel key options attributes");
156 return -EINVAL;
157 }
158
159 return opts_len;
160 }
161
---
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: 33596 bytes --]
reply other threads:[~2019-03-25 15:01 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=201903252340.RGqudbwk%lkp@intel.com \
--to=lkp@intel.com \
--cc=johannes.berg@intel.com \
--cc=kbuild-all@01.org \
--cc=linux-wireless@vger.kernel.org \
/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