linux-kernel - Re: The ext3 way of journalling

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:	Tue, 15 Jan 2008 00:13:51 +0100
From:	Alejandro Riveira Fernández 
	<ariveira@...il.com>
To:	lsorense@...lub.uwaterloo.ca (Lennart Sorensen)
Cc:	Krzysztof Halasa <khc@...waw.pl>, Tuomo Valkonen <tuomov@....fi>,
	linux-kernel@...r.kernel.org
Subject: Re: The ext3 way of journalling

El Mon, 14 Jan 2008 11:18:28 -0500
lsorense@...lub.uwaterloo.ca (Lennart Sorensen) escribió:

> On Mon, Jan 14, 2008 at 01:46:56PM +0100, Krzysztof Halasa wrote:
> > Nothing will make it work reliably if the system clock isn't stable.
> 
> I remember my nforce2 board having totally insane clock behaviour back
> around 2.6.14/2.6.15 or so.  It has since been fixed in newer kernels.

 My experience too with a Uli 1697 based mb. Estrange clock behaviour with
kernel around .15-20 but fixed now (suffering too with ext3 fsck now i use jfs)

 Back in the day i blamed the new mb but now that it runs fine i can only blame
the kernel or ubuntu user space.

> I seem to recall some ATI chipsets were even more insane than the nvidia
> at the time, with some running double speed for the system time.
> 
> --
> Len Sorensen
> --
--
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/