netfilter-devel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
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 4/9] netfilter: nft_payload: add nft_set_payload offload support
Date: Thu, 8 Aug 2019 14:07:14 +0800	[thread overview]
Message-ID: <22d05030-0791-5daa-78d3-9590e9e391dc@ucloud.cn> (raw)
In-Reply-To: <201908072022.CVdglwtY%lkp@intel.com>

This patch is also no this problem.  Because it is based on http://patchwork.ozlabs.org/patch/1140431/

On 8/7/2019 8:18 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-rhel (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_payload.c: In function 'nft_payload_set_offload':
>>> net//netfilter/nft_payload.c:571:36: error: 'struct nft_offload_reg' has no member named 'data'
>      const struct nft_data *data = &reg->data;
>                                        ^~
>
> vim +571 net//netfilter/nft_payload.c
>
>    564	
>    565	static int nft_payload_set_offload(struct nft_offload_ctx *ctx,
>    566					   struct nft_flow_rule *flow,
>    567					   const struct nft_expr *expr)
>    568	{
>    569		const struct nft_payload_set *priv = nft_expr_priv(expr);
>    570		struct nft_offload_reg *reg = &ctx->regs[priv->sreg];
>  > 571		const struct nft_data *data = &reg->data;
>    572		struct flow_action_entry *entry;
>    573		u32 len = priv->len;
>    574		u32 offset, last;
>    575		int n_actions, i;
>    576	
>    577		if (priv->base != NFT_PAYLOAD_LL_HEADER || len > 16)
>    578			return -EOPNOTSUPP;
>    579	
>    580		offset = priv->offset;
>    581		n_actions = len >> 2;
>    582		last = len & 0x3;
>    583	
>    584		for (i = 0; i < n_actions; i++) {
>    585			entry = &flow->rule->action.entries[ctx->num_actions++];
>    586	
>    587			entry->id = FLOW_ACTION_MANGLE;
>    588			entry->mangle.htype = FLOW_ACT_MANGLE_HDR_TYPE_ETH;
>    589			entry->mangle.mask = 0;
>    590			entry->mangle.val = data->data[i];
>    591			entry->mangle.offset = offset;
>    592			offset = offset + 4;
>    593		}
>    594	
>    595		if (last) {
>    596			entry = &flow->rule->action.entries[ctx->num_actions++];
>    597	
>    598			entry->id = FLOW_ACTION_MANGLE;
>    599			entry->mangle.htype = FLOW_ACT_MANGLE_HDR_TYPE_ETH;
>    600			entry->mangle.mask = ~((1 << (last * 8)) - 1);
>    601			entry->mangle.val = data->data[i];
>    602			entry->mangle.offset = offset;
>    603		}
>    604	
>    605		return 0;
>    606	}
>    607	
>
> ---
> 0-DAY kernel test infrastructure                Open Source Technology Center
> https://lists.01.org/pipermail/kbuild-all                   Intel Corporation

  reply	other threads:[~2019-08-08  6:07 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
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 [this message]
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=22d05030-0791-5daa-78d3-9590e9e391dc@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).