linux-kernel - Re: [PATCH V2] s390/sclp: pass timeout as HZ independent value

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] [day] [month] [year] [list]

Message-ID: <20150530114532.GB4218@osiris>
Date:	Sat, 30 May 2015 13:45:32 +0200
From:	Heiko Carstens <heiko.carstens@...ibm.com>
To:	Nicholas Mc Guire <hofrat@...dl.org>
Cc:	Martin Schwidefsky <schwidefsky@...ibm.com>, linux390@...ibm.com,
	linux-s390@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH V2] s390/sclp: pass timeout as HZ independent value

On Fri, May 29, 2015 at 04:50:55PM +0200, Nicholas Mc Guire wrote:
> schedule_timeout takes a timeout in jiffies but the code currently is
> passing in a constant SDIAS_SLEEP_TICKS, as this is otherwise unused
> it is replaced by 500ms as recommended by Michael Holzheu
> <holzheu@...ux.vnet.ibm.com> and converted with msecs_to_jiffies();
> As SDIAS_SLEEP_TICKS was only used in this one location it is dropped.
> 
> Patch was compile tested with (s390) defconfig + 
> CONFIG_MARCH_Z10=y, (implies CONFIG_CRASH_DUMP=y)
> 
> Patch is against 4.1-rc5 (localversion-next is -next-20150529)
> 
> Link: http://lkml.org/lkml/2015/5/29/235
> Signed-off-by: Nicholas Mc Guire <hofrat@...dl.org>
> ---
> 
> V2: timeout clarified by Heiko Carstens <heiko.carstens@...ibm.com> and
>     set to 500ms (HZ/2). And thanks for the test-config hints.
> 
>  drivers/s390/char/sclp_sdias.c |    3 +--
>  1 file changed, 1 insertion(+), 2 deletions(-)

Applied, thanks!

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/