linux-kernel - Re: [PATCH v3 1/4] time: rtc-lib: Add rtc_show_time(const char *prefix

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: <99742846-b47b-4ee5-c971-e26e8a5f935b@android.com>
Date:   Wed, 19 Jul 2017 07:52:03 -0700
From:   Mark Salyzyn <salyzyn@...roid.com>
To:     John Stultz <john.stultz@...aro.org>
Cc:     lkml <linux-kernel@...r.kernel.org>,
        "Rafael J. Wysocki" <rjw@...ysocki.net>,
        Len Brown <len.brown@...el.com>, Pavel Machek <pavel@....cz>,
        Linux PM list <linux-pm@...r.kernel.org>,
        Alessandro Zummo <a.zummo@...ertech.it>,
        Alexandre Belloni <alexandre.belloni@...e-electrons.com>,
        linux-rtc@...r.kernel.org, andy.shevchenko@...il.com,
        "Paul E. McKenney" <paulmck@...ux.vnet.ibm.com>,
        Mark Salyzyn <salyzyn@...gle.com>,
        Thierry Strudel <tstrudel@...gle.com>,
        Thomas Gleixner <tglx@...utronix.de>,
        Josh Triplett <josh@...htriplett.org>,
        Nicolas Pitre <nicolas.pitre@...aro.org>,
        Kees Cook <keescook@...omium.org>
Subject: Re: [PATCH v3 1/4] time: rtc-lib: Add rtc_show_time(const char
 *prefix_msg)

On 07/18/2017 05:00 PM, John Stultz wrote:
> On Tue, Jul 18, 2017 at 3:15 PM, Mark Salyzyn <salyzyn@...roid.com> wrote:
>> Go directly to the rtc for persistent wall clock time and print.
> So, first,  the above doesn't seem accurate to me. You're using
> getnstimeofday64() which doesn't touch the RTC.

I admit I got that backwards. I copied and pasted a line, that was 
supposed to read "We can not go" ... The point was that persistent or 
RTC clock is _not_ always available,
so we have to print suspend times when the timeofday clock is available 
at the points before suspend, and after suspend is complete.

The "Suspended for" message (in ms, we want us at least) albeit helpful, 
is performed at the bottom, and can only be reported if there is a 
persistent clock available. On most Android devices, it is not available.

I will post update, a better description in the primary patch, dropping 
the intro, printing in <epoch>.<ns> format. I asked in another thread if 
it would be OK to preserve the Legacy of RTC time format printing with 
another CONFIG parameter since we have 5 years of tooling that depends 
on that format.

-- Mark