netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Alexei Starovoitov <alexei.starovoitov@gmail.com>
To: Daniel Borkmann <daniel@iogearbox.net>, bpf <bpf@vger.kernel.org>,
	Network Development <netdev@vger.kernel.org>
Cc: Matt Mullins <mmullins@fb.com>,
	kbuild-all@01.org, Andrew Hall <hall@fb.com>
Subject: Re: [bpf:master 3/3] kernel/bpf/arraymap.c:657:36: error: invalid application of 'sizeof' to incomplete type 'struct perf_sample_data'
Date: Sat, 1 Jun 2019 08:42:21 -0700	[thread overview]
Message-ID: <CAADnVQJC5Gx5Z=2=mngHMU65fGoesMBWy5pifeDquPOhefMF-A@mail.gmail.com> (raw)
In-Reply-To: <201906011337.lBp5SlWB%lkp@intel.com>

Hi Matt,

due to this build issue I removed your commit from bpf tree.
Please fix and resubmit.

Thanks!

On Fri, May 31, 2019 at 10:48 PM kbuild test robot <lkp@intel.com> wrote:
>
> tree:   https://git.kernel.org/pub/scm/linux/kernel/git/bpf/bpf.git master
> head:   0b21b5502f561940e0d29f7ec5f840309e4a0243
> commit: 0b21b5502f561940e0d29f7ec5f840309e4a0243 [3/3] bpf: preallocate a perf_sample_data per event fd
> config: m68k-allyesconfig (attached as .config)
> compiler: m68k-linux-gcc (GCC) 7.4.0
> reproduce:
>         wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
>         chmod +x ~/bin/make.cross
>         git checkout 0b21b5502f561940e0d29f7ec5f840309e4a0243
>         # save the attached .config to linux build tree
>         GCC_VERSION=7.4.0 make.cross ARCH=m68k
>
> If you fix the issue, kindly add following tag
> Reported-by: kbuild test robot <lkp@intel.com>
>
> All errors (new ones prefixed by >>):
>
>    kernel/bpf/arraymap.c: In function 'bpf_event_entry_gen':
> >> kernel/bpf/arraymap.c:657:36: error: invalid application of 'sizeof' to incomplete type 'struct perf_sample_data'
>      ee = kzalloc(sizeof(*ee) + sizeof(struct perf_sample_data), GFP_ATOMIC);
>                                        ^~~~~~
>
> vim +657 kernel/bpf/arraymap.c
>
>    651
>    652  static struct bpf_event_entry *bpf_event_entry_gen(struct file *perf_file,
>    653                                                     struct file *map_file)
>    654  {
>    655          struct bpf_event_entry *ee;
>    656
>  > 657          ee = kzalloc(sizeof(*ee) + sizeof(struct perf_sample_data), GFP_ATOMIC);
>    658          if (ee) {
>    659                  ee->event = perf_file->private_data;
>    660                  ee->perf_file = perf_file;
>    661                  ee->map_file = map_file;
>    662                  ee->sd = (void *)ee + sizeof(*ee);
>    663          }
>    664
>    665          return ee;
>    666  }
>    667
>
> ---
> 0-DAY kernel test infrastructure                Open Source Technology Center
> https://lists.01.org/pipermail/kbuild-all                   Intel Corporation

           reply	other threads:[~2019-06-01 15:42 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <201906011337.lBp5SlWB%lkp@intel.com>]

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='CAADnVQJC5Gx5Z=2=mngHMU65fGoesMBWy5pifeDquPOhefMF-A@mail.gmail.com' \
    --to=alexei.starovoitov@gmail.com \
    --cc=bpf@vger.kernel.org \
    --cc=daniel@iogearbox.net \
    --cc=hall@fb.com \
    --cc=kbuild-all@01.org \
    --cc=mmullins@fb.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 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).