linux-ext4 - Re: [PATCH] allow internal journal size 2GB or larger

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: <AANLkTik_wVFb9=X1frJ8LWdfHLEoSm1YRg=+2p+DYbty@mail.gmail.com>
Date:	Tue, 7 Sep 2010 16:07:55 +0300
From:	"Amir G." <amir73il@...rs.sourceforge.net>
To:	Andreas Dilger <andreas.dilger@...cle.com>
Cc:	"Ted Ts'o" <tytso@....edu>,
	ext4 development <linux-ext4@...r.kernel.org>
Subject: Re: [PATCH] allow internal journal size 2GB or larger

On Thu, Aug 5, 2010 at 10:26 PM, Andreas Dilger
<andreas.dilger@...cle.com> wrote:
>
> The current libext2fs and e2fsck code does not handle an internal journal inode size larger than 2GB because of 32-bit overflow.
>

I was surprised to see this problem description, since I have been
using a 3GB journal with Next3 for a while and never observed this
problem reported by fsck.
Finally, I realized that the problem only happens when the journal
inode size is larger than 4GB.

Other than that, patch looks fine to me :-)

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