linux-kernel - Re: [PATCH v2] rtc: Add tracepoints for RTC system

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <CAK8P3a06svzg8mG1Gw9n9tqsr6rNmkzLLvirWP6wZdnCm=5_CA@mail.gmail.com>
Date:   Wed, 13 Dec 2017 09:33:23 +0100
From:   Arnd Bergmann <arnd@...db.de>
To:     Baolin Wang <baolin.wang@...aro.org>
Cc:     Alexandre Belloni <alexandre.belloni@...e-electrons.com>,
        Alessandro Zummo <a.zummo@...ertech.it>,
        Steven Rostedt <rostedt@...dmis.org>,
        Ingo Molnar <mingo@...hat.com>, linux-rtc@...r.kernel.org,
        LKML <linux-kernel@...r.kernel.org>,
        Mark Brown <broonie@...nel.org>
Subject: Re: [PATCH v2] rtc: Add tracepoints for RTC system

On Wed, Dec 13, 2017 at 6:47 AM, Baolin Wang <baolin.wang@...aro.org> wrote:
>
>>> diff --git a/include/trace/events/rtc.h b/include/trace/events/rtc.h
>>> new file mode 100644
>>> index 0000000..b5a4add
>>> --- /dev/null
>>> +++ b/include/trace/events/rtc.h
>>> +
>>
>> Also, I'm a bit concerned about having a struct rtc_time here. I think
>> its goal is mainly to have a nice representation on the time but maybe
>
> Yes.
>
>> the best would be to make printk able to pretty print the time (some
>> patches were proposed).
>
> If I understood your point correctly, you did not like the format of
> TP_printk() here, right? So how about if I remove the 'struct
> rtc_time' and just pass one 'ktime_t' parameter? But it will be not
> readable for user to trace the RTC time/alarm.
>
>>
>> How bad would that be to change it later? I didn't follow the whole
>> tracepoint ABI issue closely.

There is no general rule here other than "if it breaks for existing
users, we have to fix it". Anyone who uses the tracepoints correctly
would end up showing zero-date if we change all the fields, but
it should not crash here.

Printing a time64_t instead of rtc_time may be better here, as it's
cheaper to convert rtc_time to time64_t that vice versa. User space
looking at the trace data can then do the conversion back to struct tm
for printing in a C program or using /bin/date from a shell
script, but I agree it's an extra step.

It's also possible that we don't care about the overhead of doing
a time64_to_tm() or rtc_time64_to_tm() in the trace function, as long
as that only needs to be done if the tracepoint is active. I find trace
points a bit confusing, so I don't know if that is the case or not when
the tracepoint is compiled into the kernel but disabled at run time.

        Arnd