linux-kernel - RTC subsystem and 11 min rtc update

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:	Wed, 21 May 2008 23:57:51 +0200
From:	Philippe De Muyter <phdm@...qel.be>
To:	linux-kernel@...r.kernel.or
Subject: RTC subsystem and 11 min rtc update

Hello everybody,

I have linux-2.6.25-rc6 running on a board with an i2c rtc chip,
and synchronized to a ntp server.  When my board starts, the current
time is correctly read from the rtc chip, but ...

I noticed that my rtc chip does not get updated by the kernel every 11 min,
on my powerpc board, just like it would be on all other architectures.

Paul Mackerras told me that that is now supposed to be done by the code
inside #ifdef CONFIG_GENERIC_CMOS_UPDATE in kernel/time/ntp.c.

I agree that is a good place.

But, here CONFIG_GENERIC_CMOS_UPDATE is well defined and an i2c clock also,
and my rtc clock is not updated.  I see kernel/time/ntp.c::sync_cmos_clock
calling arch/powerpc/kernel/time.c::update_persistent_clock, where
ppc_md.set_rtc_time is NULL. ppc_md.get_rtc_time is NULL as well, but
that does not prevent the initial reading of the rtc clock during the startup
of the kernel.

Should update_persistent_clock not be directly part of the rtc subsystem,
instead of falling in a detour or a dead-end in the arch subsystem ?

Philippe
--
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/