linux-kernel - Re: [PATCH] RTC: Restore alarm after resume

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]

Message-Id: <20150105144144.46a4792e90e5800b1d865cdd@linux-foundation.org>
Date:	Mon, 5 Jan 2015 14:41:44 -0800
From:	Andrew Morton <akpm@...ux-foundation.org>
To:	Matthew Garrett <matthew.garrett@...ula.com>
Cc:	a.zummo@...ertech.it, rtc-linux@...glegroups.com,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH] RTC: Restore alarm after resume

On Mon, 22 Dec 2014 19:19:39 +0000 Matthew Garrett <matthew.garrett@...ula.com> wrote:

> Some platform firmware may interfere with the RTC alarm over suspend,
> resulting in the kernel and hardware having different ideas about system state
> but also potentially causing problems with firmware that assumes the OS will
> clean this case up. This patch saves the RTC alarm state on suspend and will
> restore it on resume if the alarm has not yet fired - if it has, it will clear
> the RTC alarm.

There's not really enough info here for me to decide which kernel
version(s) need the patch.  Can we please expand on "some"?  Any
suggestions regarding the importance/timing of the fix?


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