linux-kernel - Re: Kernel / Fliesystem Error

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

Message-Id: <080920071327.29425.46BB1642000EB0AD000072F122165258569B019B9C020A900401080C@comcast.net>
Date:	Thu, 09 Aug 2007 13:27:31 +0000
From:	cholvenstot@...cast.net
To:	"Benoit Boissinot" <bboissin@...il.com>
Cc:	"Chris Holvenstot" <saltydog@...ston.rr.com>,
	"kernel list" <linux-kernel@...r.kernel.org>
Subject: Re: Kernel / Fliesystem Error

Benoit - 

Thank you for the response - I think that you are correct in your analysis that the probem has something to do with timing and not with EXT3 itself.  

However, I have been thinking this through and this cold little shadow is now hanging over my head - there was a difference in the process used to build the system between 2.6.22.1 and 2.6.23-rcx and I would like to account for it before anyone burns their valuable time chasing ghosts I may have created.,

Specifically I am refering to the process I used ot build the initrd image.

Traditionally, I used the old standby mkinitrd whcih still builds a useable image.  However, when tracking down a series of messages about a failure to mount devfs devices I discovered that the approved method is now to use mkinitramfs.

And mkinitramfs did eliminate the messages about devfs just as the documentation said it would.

However, the initrd image for my 2.6.22.1 was built using the older mkinitrd command and it DOES NOT seem to have the timestamp issue buring boot.  With the 2.23.6-rcx series of kernels I used the mkinitramfs process - and my 2.6.23-rcx kernels is where I am seeing the problem.

I am at work now and don't have a way of seeing the early boot messages on my system at home.  When I get home this afternoon I will build the initrd image for the 2.6.22.1 system using the mkinitramfs command and I will post an updated status at that time.

Chris
 -------------- Original message ----------------------
From: "Benoit Boissinot" <bboissin@...il.com>
> On 8/9/07, Chris Holvenstot <cholvenstot@...cast.net> wrote:
> > > Chris Snook wrote:
> > >
> > >The problem here is that your clock is wrong either at mount (boot)
> > >time or unmount (shutdown) time. There's nothing wrong with ext3,
> > >except that it happens to be noticing this condition.
> >
> > 1.  This happens even when the system is rebooted via the shutdown -r
> > command - not much time for my fat fingers to get in there and dork up
> > the system clock.
> >
> > 2.  As I stated in the original note, this does NOT happen with kernel
> > 2.6.22.1 - so far I have only seen it with the 2.6.23-rc1, rc2, and
> > rc2-git1 kernels.
> >
> 
> But very likely time keeping was broken between .22 and .23-rc.
> Probably not ext3.
> 
> regards,
> 
> Benoit

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