linux-kernel - Re: Regression with sys

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

Message-ID: <a36005b50707200938y2a62616euae6a04f7248421df@mail.gmail.com>
Date:	Fri, 20 Jul 2007 09:38:49 -0700
From:	"Ulrich Drepper" <drepper@...il.com>
To:	"Takashi Iwai" <tiwai@...e.de>
Cc:	"Ingo Molnar" <mingo@...e.hu>, linux-kernel@...r.kernel.org
Subject: Re: Regression with sys_time() speedup patch

On 7/20/07, Takashi Iwai <tiwai@...e.de> wrote:
> But, is it safe to introduce another variable different from
> xtime.tv_sec?  Since xtime.tv_sec is referred in many other places,
> I'm afaid this may bring confusion...

Perhaps not if they are changed.

Somewhere where I cannot find them right now I've seen some bug
reports where the use of different time sources also caused problems.
This is no new situation.  Whenever one case uses xtime and another
case recomputed the time we have a discrepancy and this lead to
user-observable problems.

If this new variable can be used throughout it might be the right
solution.  But then there is of course the question why we have xtime
in the first place.

If/When I find the bug reports I'll point Ingo to them.
-
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/