Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67;
Subject: Re: [PATCH] selftests/seccomp: allow clock_nanosleep instead of
 nanosleep
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>
References: <20200408235753.8566-1-cascardo@canonical.com>
 <202004101328.075568852D@keescook>
From:   shuah <shuah@kernel.org>
Message-ID: <0d4e5356-d40a-8d17-1c61-d5c3c92fd11e@kernel.org>
Date:   Fri, 10 Apr 2020 14:38:58 -0600
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101
 Thunderbird/68.4.1
MIME-Version: 1.0
In-Reply-To: <202004101328.075568852D@keescook>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk

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