From: Shuah Khan <shuah@kernel.org>
To: Kees Cook <keescook@chromium.org>,
Naresh Kamboju <naresh.kamboju@linaro.org>
Cc: Anders Roxell <anders.roxell@linaro.org>,
"open list:KERNEL SELFTEST FRAMEWORK"
<linux-kselftest@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
Will Drewry <wad@chromium.org>,
Andy Lutomirski <luto@amacapital.net>,
Shuah Khan <shuahkh@osg.samsung.com>,
Shuah Khan <shuah@kernel.org>
Subject: Re: [PATCH] selftests: seccomp: fix compile error seccomp_bpf
Date: Tue, 9 Jan 2018 16:37:55 -0700 [thread overview]
Message-ID: <27f8bd36-4757-1c9c-b8b7-676483da1e0e@kernel.org> (raw)
In-Reply-To: <CAGXu5jJf1fm0X8EUE-XQCbEgWmoikt5k09YuPvKSZZ2Q=vtsJw@mail.gmail.com>
On 01/09/2018 04:25 PM, Kees Cook wrote:
> On Tue, Jan 9, 2018 at 3:24 PM, Kees Cook <keescook@chromium.org> wrote:
>> On Tue, Jan 9, 2018 at 3:07 PM, Kees Cook <keescook@chromium.org> wrote:
>>> On Fri, Jan 5, 2018 at 6:29 PM, Naresh Kamboju
>>> <naresh.kamboju@linaro.org> wrote:
>>>> On 5 January 2018 at 22:01, Anders Roxell <anders.roxell@linaro.org> wrote:
>>>>> aarch64-linux-gnu-gcc -Wl,-no-as-needed -Wall
>>>>> -lpthread seccomp_bpf.c -o seccomp_bpf
>>>>> seccomp_bpf.c: In function 'tracer_ptrace':
>>>>> seccomp_bpf.c:1720:12: error: '__NR_open' undeclared
>>>>> (first use in this function)
>>>>> if (nr == __NR_open)
>>>>> ^~~~~~~~~
>>>>> seccomp_bpf.c:1720:12: note: each undeclared identifier is reported
>>>>> only once for each function it appears in
>>>>> In file included from seccomp_bpf.c:48:0:
>>>>> seccomp_bpf.c: In function 'TRACE_syscall_ptrace_syscall_dropped':
>>>>> seccomp_bpf.c:1795:39: error: '__NR_open' undeclared
>>>>> (first use in this function)
>>>>> EXPECT_SYSCALL_RETURN(EPERM, syscall(__NR_open));
>>>>> ^
>>>>> open(2) is a legacy syscall, replaced with openat(2) since 2.6.16.
>>>>> Thus new architectures in the kernel, such as arm64, don't implement
>>>>> these legacy syscalls.
>>>>>
>>>>> Signed-off-by: Anders Roxell <anders.roxell@linaro.org>
>>>>
>>>> Thanks for the patch Anders.
>>>> Tested-by: Naresh Kamboju <naresh.kamboju@linaro.org>
>>>
>>> Did something change recently? This has built fine on arm64 for a
>>> while -- at least since commit 256d0afb11d6 ("selftests/seccomp: build
>>> and pass on arm64").
>>
>> Ah, found it. I broke it in a33b2d0359a0! :) Shuah, can you take this
>> please, with this tag added:
>>
>> Fixes: a33b2d0359a0 ("selftests/seccomp: Add tests for basic ptrace actions")
>
> And Cc to stable, as this was broken in 4.14...
>
> Cc: stable@vger.kernel.org
>
> -Kees
>
Thanks Kees. Yes I will get this into 4.16-rc1. Okay to add your
Acked-by I assume.
thanks,
-- Shuah
next prev parent reply other threads:[~2018-01-09 23:38 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-05 16:31 Anders Roxell
2018-01-06 2:29 ` Naresh Kamboju
2018-01-09 23:07 ` Kees Cook
2018-01-09 23:24 ` Kees Cook
2018-01-09 23:25 ` Kees Cook
2018-01-09 23:37 ` Shuah Khan [this message]
2018-01-09 23:46 ` Kees Cook
2018-01-10 17:04 ` Shuah Khan
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=27f8bd36-4757-1c9c-b8b7-676483da1e0e@kernel.org \
--to=shuah@kernel.org \
--cc=anders.roxell@linaro.org \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=luto@amacapital.net \
--cc=naresh.kamboju@linaro.org \
--cc=shuahkh@osg.samsung.com \
--cc=wad@chromium.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
all inboxes | Powered by JetHome®