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
| ||
|
Date: Mon, 28 Dec 2015 09:24:19 +0800 From: kernel test robot <ying.huang@...ux.intel.com> TO: Sasha Levin <sasha.levin@...cle.com> CC: Alexandre Belloni <alexandre.belloni@...e-electrons.com> Subject: [lkp] [rtc] cab572b82c: kmsg.rtc_rtc0:invalid_alarm_value FYI, we noticed the below changes on https://git.kernel.org/pub/scm/linux/kernel/git/abelloni/linux.git rtc-next commit cab572b82c4bc5f2854fdc1d42402100aa9c9683 ("rtc: fix overflow and incorrect calculation in rtc_time64_to_tm") You commit may be not the root cause. We found after your commit, there are still "invalid alarm value" in kernel log. I think that is the issue you try to resolve? [ 5.242384] rtc rtc0: invalid alarm value: 2016-1--7 0:0:0 Thanks, Ying Huang View attachment "config-4.4.0-rc6-00020-gcab572b" of type "text/plain" (143092 bytes) Download attachment "dmesg.xz" of type "application/x-xz" (13232 bytes)
Powered by blists - more mailing lists