linux-ext4 - Re: [PATCH] e2fsck: completely ignore last-mount and last-write within fudge

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

Message-Id: <40AB2046-FEAB-4F77-9FB8-D6A4C2EDFD74@redhat.com>
Date:	Wed, 1 Apr 2015 14:08:22 -0400 (EDT)
From:	Eric Sandeen <esandeen@...hat.com>
To:	"Theodore Ts'o" <tytso@....edu>
Cc:	Jan Kara <jack@...e.cz>, Eric Sandeen <sandeen@...hat.com>,
	ext4 development <linux-ext4@...r.kernel.org>
Subject: Re: [PATCH] e2fsck: completely ignore last-mount and last-write within fudge_time


> On Apr 1, 2015, at 11:08 AM, Theodore Ts'o <tytso@....edu> wrote:
> 
> On Wed, Apr 01, 2015 at 03:06:42PM +0200, Jan Kara wrote:
>>>    e2fsck: use PROMPT_NONE for FUTURE_SB_LAST_*_FUDGED problems
>>> 
>>>    This allows us to print a message warning the user that there is
>>>    something funny going on with their hardware clock (probably time zone
>>>    issues caused by trying to be compatible with legacy OS's such as
>>>    Windows), without triggering a full file system check.
>>> 
>>>    Signed-off-by: Theodore Ts'o <tytso@....edu>
>>  OK, so this will just print the error but won't fix it unless in preen
>> or full check mode. Am I right. That sounds fine to me.
> 
> Actually, it will fix it unless the run in -n mode, but it won't count
> it as a "fix".  Hence, it won't trigger the full file system check.
> 
>                                       - Ted

Avoiding the full check is my only real concern so that's fine.  Docs might need updates.

-Eric--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html