From: Daniel Borkmann <daniel@iogearbox.net>
To: kbuild test robot <lkp@intel.com>
Cc: kbuild-all@01.org, davem@davemloft.net, ast@fb.com,
netdev@vger.kernel.org
Subject: Re: [PATCH net 2/2] bpf: fix overflow in prog accounting
Date: Sat, 17 Dec 2016 11:03:43 +0100 [thread overview]
Message-ID: <58550D7F.4060102@iogearbox.net> (raw)
In-Reply-To: <201612171034.Pd1bvSuT%fengguang.wu@intel.com>
On 12/17/2016 03:52 AM, kbuild test robot wrote:
> Hi Daniel,
>
> [auto build test ERROR on net/master]
>
> url: https://github.com/0day-ci/linux/commits/Daniel-Borkmann/bpf-dynamically-allocate-digest-scratch-buffer/20161217-090046
> config: sparc-defconfig (attached as .config)
> compiler: sparc-linux-gcc (GCC) 6.2.0
> reproduce:
> wget https://git.kernel.org/cgit/linux/kernel/git/wfg/lkp-tests.git/plain/sbin/make.cross -O ~/bin/make.cross
> chmod +x ~/bin/make.cross
> # save the attached .config to linux build tree
> make.cross ARCH=sparc
>
> All errors (new ones prefixed by >>):
>
> kernel/bpf/core.c: In function '__bpf_prog_charge':
>>> kernel/bpf/core.c:80:50: error: 'struct user_struct' has no member named 'locked_vm'; did you mean 'locked_shm'?
> user_bufs = atomic_long_add_return(pages, &user->locked_vm);
> ^~
> kernel/bpf/core.c:82:32: error: 'struct user_struct' has no member named 'locked_vm'; did you mean 'locked_shm'?
> atomic_long_sub(pages, &user->locked_vm);
> ^~
> kernel/bpf/core.c: In function '__bpf_prog_uncharge':
> kernel/bpf/core.c:93:31: error: 'struct user_struct' has no member named 'locked_vm'; did you mean 'locked_shm'?
> atomic_long_sub(pages, &user->locked_vm);
Argh, right, I'll send v2 later today.
next prev parent reply other threads:[~2016-12-17 10:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-17 0:54 [PATCH net 0/2] Two BPF fixes Daniel Borkmann
2016-12-17 0:54 ` [PATCH net 1/2] bpf: dynamically allocate digest scratch buffer Daniel Borkmann
2016-12-17 0:54 ` [PATCH net 2/2] bpf: fix overflow in prog accounting Daniel Borkmann
2016-12-17 2:52 ` kbuild test robot
2016-12-17 10:03 ` Daniel Borkmann [this message]
2016-12-17 3:15 ` kbuild test robot
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=58550D7F.4060102@iogearbox.net \
--to=daniel@iogearbox.net \
--cc=ast@fb.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.