linux-ext4 - Re: [PATCH] resize2fs: handle exactly-16T filesystems in resize2fs

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:	Fri, 17 Dec 2010 09:06:21 +0100
From:	Stephan Boettcher <boettcher@...sik.uni-kiel.de>
To:	"Ted Ts'o" <tytso@....edu>
Cc:	ext4 development <linux-ext4@...r.kernel.org>
Subject: Re: [PATCH] resize2fs: handle exactly-16T filesystems in resize2fs

"Ted Ts'o" <tytso@....edu> writes:

> The 1.42 version is on the main "master" and "next" branch, where
> "next" is where I'll check in things initially, and then "master"
> catches up with "next".  I took this from git, with the basic idea
> being that if there are people who are testing next, and people who
> are using the "master", hopefully problems get noticed and fixed
> before people are using "master" grab a commit.  To be honest there
> probably aren't enough people tracking next and master for this to
> make a huge amount of difference, but I'm following this scheme
> anyway.

So, I am doing the right thing, when I use the master branch for my 20TB
filesystem? Or shall I try next, at least until I decide to actually use
the filesystem for something real?

-- 
Stephan

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