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]
Date:	Wed, 7 May 2008 11:14:47 -0700 (PDT)
From:	Martin Knoblauch <spamtrap@...bisoft.de>
To:	john stultz <johnstul@...ibm.com>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: 2.6.25.2 - Jiffies/Time jumping back and forth (Regereesion from 2.6.24)

----- Original Message ----

> From: john stultz <johnstul@...ibm.com>
> To: Martin Knoblauch <spamtrap@...bisoft.de>
> Cc: linux-kernel@...r.kernel.org
> Sent: Wednesday, May 7, 2008 7:07:49 PM
> Subject: Re: 2.6.25.2 - Jiffies/Time jumping back and forth (Regereesion from 2.6.24)
> 
> On Wed, May 7, 2008 at 5:42 AM, Martin Knoblauch wrote:
> > Hi,
> >
> >   any news on the one below? I upgraded to 2.6.25.2 and the problem still 
> persists. Would adding a bugzilla actually help ? :-)
> >
> >
> >  http://www.ussg.iu.edu/hypermail/linux/kernel/0804.2/1144.html
> 
> With this issue you're seeing is only the printk timestamps jumping
> back, correct?
>

 correct.

> For example, you're not seeing the output from gettimeofday() or the
> actual jiffies value (as seen from maybe a driver) jump backward? Is
> that right?
> 

 correct again. As far as I can see, other time related things seem to be OK, including gettimeofday.

> The printk timestamps may jump around a bit at bootup,  especially if
> you have unsynced TSCs, so that is a known issue. However its not
> known to have any actual negative effect other then maybe causing the
> dmesg log to be a bit confusing.
> 

 the problem, is not just at bootup and the jumping. During the *complete* lifetime of the kernel I see:

a) the dmesg timestamps jumping back and forth
b) the values are much to small and have absolutely no relation to "seconds after bootup", as they have with 2.6.24 and before.

 But you are right, it might not be a jiffie problem, but a "dmesg timestamp" thing.

Cheers
Martin

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

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ