linux-ext4 - Re: [RFC] support multiple max offset limits for a single superblock

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:	Fri, 30 Nov 2007 09:14:14 -0800
From:	Chris Wedgwood <cw@...f.org>
To:	Eric Sandeen <sandeen@...deen.net>
Cc:	linux-fsdevel <linux-fsdevel@...r.kernel.org>,
	ext4 development <linux-ext4@...r.kernel.org>
Subject: Re: [RFC] support multiple max offset limits for a single
	superblock

On Fri, Nov 30, 2007 at 10:35:01AM -0600, Eric Sandeen wrote:

> I could do the same for ext4, but Chris Mason prodded me to think of something
> more generic... this is what I came up with.

I think it (for now) should remain in the few file-systems that are
affected to avoid making a new ->i_op right now.  If it turns out this
is a more commonly need in the future we could do this, but it seems a
bit heavy handy just yet given at present.

Also, it might turn at that it makes sense to to on-the-fly conversion
in the filesystem (where applicable) at some later stage, so this
wouldn't be useful there.  I assume it's probably hard to convert a
large bitmap-based ext4 file to an extent-based one (how large can a
transaction be?) but that might not always be the case and it's
probably fine for smaller files.

> (BTW another option would be to convert old-format files when
> accessed, but that has its own set of tradeoffs...)

I think doing that where possible makes more sense.  As I said above
I'm not sure how easy that is to do for all files, but then again fsck
could take care of those if prodded.
-
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