lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <f7db39bd-d11e-4854-8b6e-2543aeec1d70@amazon.com>
Date: Mon, 19 Feb 2024 15:06:42 +0000
From: "Mohamed Abuelfotoh, Hazem" <abuehaze@...zon.com>
To: Kees Cook <keescook@...omium.org>, SeongJae Park <sj@...nel.org>
CC: <shuah@...nel.org>, <linux-kselftest@...r.kernel.org>,
	<linux-kernel@...r.kernel.org>, <stable@...r.kernel.org>,
	<Vijaikumar_Kanagarajan@...tor.com>, <brauner@...nel.org>,
	<jlayton@...nel.org>, <jack@...e.cz>
Subject: Re: [PATCH] selftests/mqueue: Set timeout to 100 seconds

On 17/02/2024 00:01, Kees Cook wrote:

> 
> Should it be 100 or 180? Either way:
> 
> Reviewed-by: Kees Cook <keescook@...omium.org>
> 
> --
> Kees Cook

Both options may work, I am more inclined to have this as 180 seconds by 
giving more time for the test to finish, this can be reduced later to 
100 or something else if we start hearing complains about the new timeout.

Hazem

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ