From: wenxu <wenxu@ucloud.cn>
To: kbuild test robot <lkp@intel.com>
Cc: kbuild-all@01.org, pablo@netfilter.org, fw@strlen.de,
netfilter-devel@vger.kernel.org
Subject: Re: [PATCH nf-next v3 3/9] netfilter: nft_fwd_netdev: add fw_netdev action support
Date: Thu, 8 Aug 2019 14:06:46 +0800 [thread overview]
Message-ID: <7557d542-c47b-3c1c-e428-28a03e1162be@ucloud.cn> (raw)
In-Reply-To: <201908072042.KC67W3dl%lkp@intel.com>
This patch is no this problem. Because it is based on http://patchwork.ozlabs.org/patch/1140431/
On 8/7/2019 8:15 PM, kbuild test robot wrote:
> Hi,
>
> Thank you for the patch! Yet something to improve:
>
> [auto build test ERROR on nf-next/master]
>
> url: https://github.com/0day-ci/linux/commits/wenxu-ucloud-cn/netfilter-nf_tables_offload-support-more-expr-and-obj-offload/20190804-144846
> base: https://kernel.googlesource.com/pub/scm/linux/kernel/git/pablo/nf-next.git master
> config: x86_64-allyesconfig (attached as .config)
> compiler: gcc-7 (Debian 7.4.0-10) 7.4.0
> reproduce:
> # save the attached .config to linux build tree
> make ARCH=x86_64
>
> If you fix the issue, kindly add following tag
> Reported-by: kbuild test robot <lkp@intel.com>
>
> All errors (new ones prefixed by >>):
>
> net/netfilter/nft_fwd_netdev.c: In function 'nft_fwd_netdev_offload':
>>> net/netfilter/nft_fwd_netdev.c:73:36: error: 'struct nft_offload_reg' has no member named 'data'
> const struct nft_data *data = ®->data;
> ^~
>
> vim +73 net/netfilter/nft_fwd_netdev.c
>
> 66
> 67 static int nft_fwd_netdev_offload(struct nft_offload_ctx *ctx,
> 68 struct nft_flow_rule *flow,
> 69 const struct nft_expr *expr)
> 70 {
> 71 const struct nft_fwd_netdev *priv = nft_expr_priv(expr);
> 72 struct nft_offload_reg *reg = &ctx->regs[priv->sreg_dev];
> > 73 const struct nft_data *data = ®->data;
> 74 struct flow_action_entry *entry;
> 75 struct net_device *dev;
> 76 int oif = -1;
> 77
> 78 entry = &flow->rule->action.entries[ctx->num_actions++];
> 79
> 80 memcpy(&oif, data->data, sizeof(oif));
> 81 dev = __dev_get_by_index(ctx->net, oif);
> 82 if (!dev)
> 83 return -EOPNOTSUPP;
> 84
> 85 entry->id = FLOW_ACTION_REDIRECT;
> 86 entry->dev = dev;
> 87
> 88 return 0;
> 89 }
> 90
>
> ---
> 0-DAY kernel test infrastructure Open Source Technology Center
> https://lists.01.org/pipermail/kbuild-all Intel Corporation
next prev parent reply other threads:[~2019-08-08 6:06 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-01 14:01 [PATCH nf-next v3 0/9] netfilter: nf_tables_offload: support more expr and obj offload wenxu
2019-08-01 14:01 ` [PATCH nf-next v3 1/9] netfilter: nf_flow_offload: add net in offload_ctx wenxu
2019-08-01 14:01 ` [PATCH nf-next v3 2/9] netfilter: nf_tables_offload: add offload_actions callback wenxu
2019-08-01 14:01 ` [PATCH nf-next v3 3/9] netfilter: nft_fwd_netdev: add fw_netdev action support wenxu
2019-08-07 12:15 ` kbuild test robot
2019-08-08 6:06 ` wenxu [this message]
2019-08-01 14:01 ` [PATCH nf-next v3 4/9] netfilter: nft_payload: add nft_set_payload offload support wenxu
2019-08-07 12:18 ` kbuild test robot
2019-08-08 6:07 ` wenxu
2019-08-01 14:01 ` [PATCH nf-next v3 5/9] netfilter: nft_tunnel: support NFT_TUNNEL_SRC/DST_IP match wenxu
2019-08-13 18:19 ` Pablo Neira Ayuso
2019-08-14 7:54 ` wenxu
2019-08-14 8:00 ` Pablo Neira Ayuso
2019-08-14 8:19 ` Pablo Neira Ayuso
2019-08-14 8:28 ` wenxu
2019-08-14 9:17 ` Pablo Neira Ayuso
2019-08-14 8:22 ` wenxu
2019-08-01 14:01 ` [PATCH nf-next v3 6/9] netfilter: nft_tunnel: support tunnel meta match offload wenxu
2019-08-01 14:01 ` [PATCH nf-next v3 7/9] netfilter: nft_tunnel: add NFTA_TUNNEL_KEY_RELEASE action wenxu
2019-08-01 14:01 ` [PATCH nf-next v3 8/9] netfilter: nft_objref: add nft_objref_type offload wenxu
2019-08-01 14:01 ` [PATCH nf-next v3 9/9] netfilter: nft_tunnel: support nft_tunnel_obj offload wenxu
2019-08-13 10:58 ` [PATCH nf-next v3 0/9] netfilter: nf_tables_offload: support more expr and obj offload wenxu
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=7557d542-c47b-3c1c-e428-28a03e1162be@ucloud.cn \
--to=wenxu@ucloud.cn \
--cc=fw@strlen.de \
--cc=kbuild-all@01.org \
--cc=lkp@intel.com \
--cc=netfilter-devel@vger.kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).