linux-kernel - Re: [PATCH 0/4] clocksource/vt8500: Fix hangs in small delays

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]

Date:	Mon, 21 Dec 2015 11:29:16 +0300
From:	Roman Volkov <v1ron@...l.ru>
To:	Daniel Lezcano <daniel.lezcano@...aro.org>,
	Thomas Gleixner <tglx@...utronix.de>,
	Alexey Charkov <alchark@...il.com>,
	Arnd Bergmann <arnd@...db.de>
Cc:	Tony Prisk <linux@...sktech.co.nz>,
	linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org,
	Roman Volkov <rvolkov@...os.org>
Subject: Re: [PATCH 0/4] clocksource/vt8500: Fix hangs in small delays

On Mon, 21 Dec 2015 01:28:08 +0300
Roman Volkov <v1ron@...l.ru> wrote:

> From: Roman Volkov <rvolkov@...os.org>
> 
> vt8500 hangs in nanosleep() function, starting from commit
> c6eb3f70d4482806dc2d3e1e3c7736f497b1d418, making the system unusable.
> Per investigation, looks like set_next_event() now receives too small
> delta and fails with -ETIME.
> 
> Google group discussion:
> https://groups.google.com/forum/#!topic/vt8500-wm8505-linux-kernel/vDMF_mDOb1k
> 
> Roman Volkov (4):
>   clocksource/vt8500: Use [read\write]l_relaxed()
>   clocksource/vt8500: Remove the 'loops' variable
>   clocksource/vt8500: Use MIN_OSCR_DELTA from PXA
>   clocksource/vt8500: Add register R/W functions
> 
>  drivers/clocksource/vt8500_timer.c | 98
> +++++++++++++++++++++++++++----------- 1 file changed, 69
> insertions(+), 29 deletions(-)
> 

Please note that vt8500 maintainer (Tony Prisk) was silent in the last
year. Any suggestions on this?

Regards,
Roman
--
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/