From: Daniel Borkmann <daniel@iogearbox.net>
To: Joel Fernandes <joelaf@google.com>, linux-kernel@vger.kernel.org
Cc: netdev@vger.kernel.org, alison@she-devel.com, juri.lelli@arm.com,
fengc@google.com, davem@davemloft.net, ast@kernel.org,
kernel-team@android.com
Subject: Re: [PATCH v4 1/4] samples/bpf: Use getppid instead of getpgrp for array map stress
Date: Wed, 20 Sep 2017 23:24:28 +0200 [thread overview]
Message-ID: <59C2DC8C.1080504@iogearbox.net> (raw)
In-Reply-To: <20170920161159.25747-1-joelaf@google.com>
On 09/20/2017 06:11 PM, Joel Fernandes wrote:
> When cross-compiling the bpf sample map_perf_test for aarch64, I find that
> __NR_getpgrp is undefined. This causes build errors. This syscall is deprecated
> and requires defining __ARCH_WANT_SYSCALL_DEPRECATED. To avoid having to define
> that, just use a different syscall (getppid) for the array map stress test.
>
> Acked-by: Alexei Starovoitov <ast@kernel.org>
> Signed-off-by: Joel Fernandes <joelaf@google.com>
Acked-by: Daniel Borkmann <daniel@iogearbox.net>
prev parent reply other threads:[~2017-09-20 21:24 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-20 16:11 [PATCH v4 1/4] samples/bpf: Use getppid instead of getpgrp for array map stress Joel Fernandes
2017-09-20 16:11 ` [PATCH v4 2/4] samples/bpf: Enable cross compiler support Joel Fernandes
2017-09-20 21:24 ` Daniel Borkmann
2017-09-20 16:11 ` [PATCH v4 3/4] samples/bpf: Fix pt_regs issues when cross-compiling Joel Fernandes
2017-09-20 21:25 ` Daniel Borkmann
2017-09-20 16:11 ` [PATCH v4 4/4] samples/bpf: Add documentation on cross compilation Joel Fernandes
2017-09-20 16:50 ` Randy Dunlap
2017-09-20 21:25 ` Daniel Borkmann
2017-09-20 21:24 ` 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=59C2DC8C.1080504@iogearbox.net \
--to=daniel@iogearbox.net \
--cc=alison@she-devel.com \
--cc=ast@kernel.org \
--cc=davem@davemloft.net \
--cc=fengc@google.com \
--cc=joelaf@google.com \
--cc=juri.lelli@arm.com \
--cc=kernel-team@android.com \
--cc=linux-kernel@vger.kernel.org \
--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.