From: kernel test robot <lkp@intel.com>
To: Pablo Neira Ayuso <pablo@netfilter.org>
Cc: llvm@lists.linux.dev, kbuild-all@lists.01.org,
linux-kernel@vger.kernel.org, Lukas Wunner <lukas@wunner.de>
Subject: [l1k:nft_egress_v6 5/6] net/netfilter/nft_fwd_netdev.c:32:2: error: use of undeclared identifier 'skb'
Date: Tue, 12 Oct 2021 00:23:23 +0800 [thread overview]
Message-ID: <202110120015.GLEMggM9-lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2152 bytes --]
tree: https://github.com/l1k/linux nft_egress_v6
head: bacabad3aa520ee674afbdc348b2010e583ab20c
commit: fcf97a4df9fc1f01e3030ab439787f54af1a1088 [5/6] netfilter: nft_fwd_netdev: Support egress hook
config: i386-randconfig-r036-20211011 (attached as .config)
compiler: clang version 14.0.0 (https://github.com/llvm/llvm-project 903b30fea21f99d8f48fde4defcc838970e30ee1)
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
# https://github.com/l1k/linux/commit/fcf97a4df9fc1f01e3030ab439787f54af1a1088
git remote add l1k https://github.com/l1k/linux
git fetch --no-tags l1k nft_egress_v6
git checkout fcf97a4df9fc1f01e3030ab439787f54af1a1088
# save the attached .config to linux build tree
mkdir build_dir
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=clang make.cross W=1 O=build_dir ARCH=i386 SHELL=/bin/bash
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>
All errors (new ones prefixed by >>):
>> net/netfilter/nft_fwd_netdev.c:32:2: error: use of undeclared identifier 'skb'
skb->skb_iif = skb->dev->ifindex;
^
net/netfilter/nft_fwd_netdev.c:32:17: error: use of undeclared identifier 'skb'
skb->skb_iif = skb->dev->ifindex;
^
2 errors generated.
vim +/skb +32 net/netfilter/nft_fwd_netdev.c
23
24 static void nft_fwd_netdev_eval(const struct nft_expr *expr,
25 struct nft_regs *regs,
26 const struct nft_pktinfo *pkt)
27 {
28 struct nft_fwd_netdev *priv = nft_expr_priv(expr);
29 int oif = regs->data[priv->sreg_dev];
30
31 /* This is used by ifb only. */
> 32 skb->skb_iif = skb->dev->ifindex;
33 skb_set_redirected(pkt->skb, nft_hook(pkt) == NF_NETDEV_INGRESS);
34
35 nf_fwd_netdev_egress(pkt, oif);
36 regs->verdict.code = NF_STOLEN;
37 }
38
---
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: 30744 bytes --]
reply other threads:[~2021-10-11 16:24 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=202110120015.GLEMggM9-lkp@intel.com \
--to=lkp@intel.com \
--cc=kbuild-all@lists.01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=lukas@wunner.de \
--cc=pablo@netfilter.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