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]

Message-ID: <b6c5339f0801140810s54ab5d39t2eb2d97c253089b0@mail.gmail.com>
Date:	Mon, 14 Jan 2008 11:10:54 -0500
From:	me@...copeland.com
To:	"Tuomo Valkonen" <tuomov@....fi>
Cc:	"Theodore Tso" <tytso@....edu>, linux-kernel@...r.kernel.org
Subject: Re: The ext3 way of journalling

On 1/14/08, Tuomo Valkonen <tuomov@....fi> wrote:
> On 2008-01-13 18:11 -0500, Theodore Tso wrote:
> > It's much more likely that this early in your boot cycle, your clock is
> > sometimes incorrect.
>
> I doubt it. I get this nearly _always_ when the system crashes, which
> accounts for the vast majority of the times I boot it. (I wish swsusp
> didn't suck so much..)

It sounds like you have CONFIG_PM_TRACE turned on.  From the Kconfig help:

    This enables some cheesy code to save the last PM event point in the
    RTC across reboots, so that you can debug a machine that just hangs
    during suspend (or more commonly, during resume).

[...]

    CAUTION: this option will cause your machine's real-time clock to be
    set to an invalid time after a resume.

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