linux-kernel - behavior of hrtimers scheduled to expire in the past

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-next>] [day] [month] [year] [list]

Message-ID: <4b6fba110810201724v41d26dd8lc9abcba129599fd1@mail.gmail.com>
Date:	Mon, 20 Oct 2008 20:24:38 -0400
From:	"Daniel Rosenthal" <danielrosenthal@....org>
To:	LKML <linux-kernel@...r.kernel.org>, "Ingo Molnar" <mingo@...e.hu>,
	"Thomas Gleixner" <tglx@...utronix.de>
Subject: behavior of hrtimers scheduled to expire in the past

What is the intended behavior for an hrtimer that is scheduled to
expire in the past?  I assumed that it would simply be scheduled to
expire at the nearest available time in the future, but I wrote some
scheduler code and it looks like hrtimers don't go off at all if they
are not scheduled to go off at a time which is after rq->clock.  Is
this the intended behavior or is this a bug?

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