linux-kernel - Re: [PATCH v5 0/9] rtc-cmos,rtc-mc146818-lib: fixes

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:   Fri, 7 Jan 2022 14:14:58 +0100
From:   Mateusz Jończyk <mat.jonczyk@...pl>
To:     Alexandre Belloni <alexandre.belloni@...tlin.com>
Cc:     linux-rtc@...r.kernel.org, linux-kernel@...r.kernel.org,
        Alessandro Zummo <a.zummo@...ertech.it>
Subject: Re: [PATCH v5 0/9] rtc-cmos,rtc-mc146818-lib: fixes

W dniu 07.01.2022 o 14:03, Alexandre Belloni pisze:
> Hi,
>
> On 07/01/2022 13:49:25+0100, Mateusz Jończyk wrote:
[snip]
>> v5: Increase maximum accepted duration of the UIP high pulse from 10 to 20ms,
>>     in case there are some very slow chips out there.
>>
>>     Note: this may cause problems with hpet_rtc_interrupt() if the CMOS
>>     RTC stops working while the system is running and RTC update
>>     interrupt / RTC alarm interrupt is enabled (which should be rare).
>>     In this case, hpet_rtc_interrupt() is executed 64 times per second
>>     and takes up to 20ms to complete - which may constantly occupy
>>     one CPU. I am not sure if this is likely enough to implement
>>     special handling of this case in hpet_rtc_interrupt().
>>
> Because v4 has been applied, 

Nice, thank you! I didn't know about this.

> you'd have to send a series against rtc-next.

OK

Greetings,

Mateusz