From: shuah <shuah@kernel.org>
To: Kees Cook <keescook@chromium.org>,
Thadeu Lima de Souza Cascardo <cascardo@canonical.com>
Cc: bpf@vger.kernel.org, netdev@vger.kernel.org,
linux-kselftest@vger.kernel.org, linux-kernel@vger.kernel.org,
luto@amacapital.net, wad@chromium.org, shuah <shuah@kernel.org>
Subject: Re: [PATCH] selftests/seccomp: allow clock_nanosleep instead of nanosleep
Date: Fri, 10 Apr 2020 14:38:58 -0600 [thread overview]
Message-ID: <0d4e5356-d40a-8d17-1c61-d5c3c92fd11e@kernel.org> (raw)
In-Reply-To: <202004101328.075568852D@keescook>
On 4/10/20 2:29 PM, Kees Cook wrote:
> On Wed, Apr 08, 2020 at 08:57:53PM -0300, Thadeu Lima de Souza Cascardo wrote:
>> glibc 2.31 calls clock_nanosleep when its nanosleep function is used. So
>> the restart_syscall fails after that. In order to deal with it, we trace
>> clock_nanosleep and nanosleep. Then we check for either.
>>
>> This works just fine on systems with both glibc 2.30 and glibc 2.31,
>> whereas it failed before on a system with glibc 2.31.
>>
>> Signed-off-by: Thadeu Lima de Souza Cascardo <cascardo@canonical.com>
>
> Actually, sorry, this should go via Shuah's tree. :) Shuah, do you have
> anything going Linus's way already for -rc2?
>
> Acked-by: Kees Cook <keescook@chromium.org>
>
I have a few patches for rc2. I will pick this up.
thanks,
-- Shuah
prev parent reply other threads:[~2020-04-10 20:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-08 23:57 [PATCH] selftests/seccomp: allow clock_nanosleep instead of nanosleep Thadeu Lima de Souza Cascardo
2020-04-10 20:26 ` Kees Cook
2020-04-10 20:29 ` Kees Cook
2020-04-10 20:38 ` shuah [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=0d4e5356-d40a-8d17-1c61-d5c3c92fd11e@kernel.org \
--to=shuah@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=cascardo@canonical.com \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=luto@amacapital.net \
--cc=netdev@vger.kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).