linux-kernel - Re: [PATCH 3/3] [RFC] hrtimer: Update hrtimer base offsets each hrtimer

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:	Thu, 05 Jul 2012 10:30:03 -0400
From:	Prarit Bhargava <prarit@...hat.com>
To:	John Stultz <johnstul@...ibm.com>
CC:	Linux Kernel <linux-kernel@...r.kernel.org>,
	stable@...r.kernel.org, Thomas Gleixner <tglx@...utronix.de>,
	linux@...nhuawei.org
Subject: Re: [PATCH 3/3] [RFC] hrtimer: Update hrtimer base offsets each hrtimer_interrupt



On 07/04/2012 02:21 AM, John Stultz wrote:
> This patch introduces a new funciton which captures the
> CLOCK_MONOTONIC time, along with the CLOCK_REALTIME and
> CLOCK_BOOTTIME offsets at the same moment. This new function
> is then used in place of ktime_get() when hrtimer_interrupt()
> is expiring timers.
> 
> This ensures that any changes to realtime or boottime offsets
> are noticed and stored into the per-cpu hrtimer base structures,
> prior to doing any hrtimer expiration. This should ensure that
> timers are not expired early if the offsets changes under us.
> 
> This is useful in the case where clock_was_set() is called from
> atomic context and have to schedule the hrtimer base offset update
> via a timer, as it provides extra robustness in the face of any
> possible timer delay.
> 
> CC: Prarit Bhargava <prarit@...hat.com>
> CC: stable@...r.kernel.org
> CC: Thomas Gleixner <tglx@...utronix.de>
> CC: linux@...nhuawei.org
> Signed-off-by: John Stultz <johnstul@...ibm.com>

Acked-by: Prarit Bhargava <prarit@...hat.com>

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