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

Message-Id: <1186658730.7018.8.camel@localhost>
Date:	Thu, 09 Aug 2007 06:25:30 -0500
From:	Chris Holvenstot <cholvenstot@...cast.net>
To:	Chris Holvenstot <saltydog@...ston.rr.com>
Cc:	kernel list <linux-kernel@...r.kernel.org>
Subject: Re: Kernel / Fliesystem Error

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

Chris - 

I appreciate the response but on the face of it I do not know if I
believe that this is the answer.  I am not the sharpest knife in the
drawer but the following two items still cast a doubt on the answer.

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.

Other than this I would say you were spot on in your analysis.  Maybe
there is something I don't understand here.  If so, pardon me for being
"Thick as a brick" 

Chris

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