linux-ext4 - Re: Repost (from LKML): EXT3 FS and 64K blocks 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: <20100710002611.GA17032@thunk.org>
Date:	Fri, 9 Jul 2010 20:26:11 -0400
From:	Ted Ts'o <tytso@....edu>
To:	Daniel Taylor <Daniel.Taylor@....com>
Cc:	linux-ext4@...r.kernel.org
Subject: Re: Repost (from LKML): EXT3 FS and 64K blocks error

On Fri, Jul 09, 2010 at 03:32:22PM -0700, Daniel Taylor wrote:
> We're switching to ext4.  I just thought someone might want to take
> a look at the error message.  I can do some more testing, next
> week, if there are suggestions of what to try.

I can try to dig up the patch we used to fix 64k block sizes for ext4,
and backport it to ext3, but to be honest I'm pretty overbooked
already as it is, and in general we've been trying to keep ext3
stable, which means in practice, bug fixes only.  The question is
whether 64k blocksize support is considered a bug fix or a new
feature....  so if you're switching to ext4 anyway, I'd probably just
not bother trying to fix it for ext3...

					- 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