linux-ext4 - Re: [PATCH] resize2fs: relax requirements for -P output a bit

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]

Date:	Sat, 17 Jul 2010 06:37:50 -0400
From:	Ted Ts'o <tytso@....edu>
To:	Eric Sandeen <sandeen@...hat.com>
Cc:	ext4 development <linux-ext4@...r.kernel.org>
Subject: Re: [PATCH] resize2fs: relax requirements for -P output a bit

On Mon, Jul 12, 2010 at 01:27:44PM -0500, Eric Sandeen wrote:
> Requiring an immediate pre-fsck before printing a minimum
> resize size seems a bit draconian; if the fs isn't clean or marked
> with error, then certainly, but for an informational minimum
> size, I don't think we need to require a fsck since last mount.
> 
> I had simply copied the checks from the actual resize path,
> previously.
> 
> Installers use this option (-P) to gather minimum resize info,
> and requiring an actual fsck before use just seems to go too far.
> 
> Signed-off-by: Eric Sandeen <sandeen@...hat.com>

Makes sense.  I've added it to the e2fsprogs maint branch.

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