All of lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel Borkmann <daniel@iogearbox.net>
To: kbuild test robot <lkp@intel.com>
Cc: kbuild-all@01.org, davem@davemloft.net,
	alexei.starovoitov@gmail.com, netdev@vger.kernel.org
Subject: Re: [PATCH net-next] bpf: add skb_postpush_rcsum and fix dev_forward_skb occasions
Date: Thu, 07 Jan 2016 10:05:41 +0100	[thread overview]
Message-ID: <568E2A65.2020001@iogearbox.net> (raw)
In-Reply-To: <201601071158.XIjinbYM%fengguang.wu@intel.com>

On 01/07/2016 04:22 AM, kbuild test robot wrote:
> Hi Daniel,
>
> [auto build test ERROR on net-next/master]
>
> url:    https://github.com/0day-ci/linux/commits/Daniel-Borkmann/bpf-add-skb_postpush_rcsum-and-fix-dev_forward_skb-occasions/20160107-090423
> config: x86_64-lkp (attached as .config)
> reproduce:
>          # save the attached .config to linux build tree
>          make ARCH=x86_64
>
> All errors (new ones prefixed by >>):
>
>     In file included from include/net/sch_generic.h:8:0,
>                      from include/linux/filter.h:16,
>                      from include/net/sock.h:64,
>                      from include/net/inet_sock.h:27,
>                      from include/net/ip.h:30,
>                      from net/core/filter.c:34:
>     net/core/filter.c: In function 'bpf_clone_redirect':
>>> net/core/filter.c:1530:19: error: 'struct sk_buff' has no member named 'tc_verd'
>        if (G_TC_AT(skb2->tc_verd) & AT_INGRESS)

Hmm, right. I'll add an extra helper function then for v2 as we also
have such ifdef/else in other places for accessing tc_verd.

Thanks,
Daniel

      reply	other threads:[~2016-01-07  9:05 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-07  1:01 [PATCH net-next] bpf: add skb_postpush_rcsum and fix dev_forward_skb occasions Daniel Borkmann
2016-01-07  1:53 ` Hannes Frederic Sowa
2016-01-07 10:02   ` Daniel Borkmann
2016-01-07  3:22 ` kbuild test robot
2016-01-07  9:05   ` Daniel Borkmann [this message]

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=568E2A65.2020001@iogearbox.net \
    --to=daniel@iogearbox.net \
    --cc=alexei.starovoitov@gmail.com \
    --cc=davem@davemloft.net \
    --cc=kbuild-all@01.org \
    --cc=lkp@intel.com \
    --cc=netdev@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.