linux-ext4 - Re: journal recovery problems with metadata

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: <20140809002131.GR25145@thunk.org>
Date:	Fri, 8 Aug 2014 20:21:31 -0400
From:	Theodore Ts'o <tytso@....edu>
To:	TR Reardon <thomas_reardon@...mail.com>
Cc:	linux-ext4@...r.kernel.org
Subject: Re: journal recovery problems with metadata_csum, *non-64bit*

On Fri, Aug 08, 2014 at 06:29:40PM -0400, TR Reardon wrote:
> 
> Using master @ de25d9c8c48c7474828e9452184e204b18b8e090, which was the
> 1.42.11 release.  The current master and next have same problem.

What's going on is that the "master" and "next" branches on the
e2fsprogs git tree are development branches which will eventually be
the 1.43.0 release.  The "maint" branch is where the 1.42.x releases
are cut.

The maint branch does not have metadata_csum and inline_data support
at all.  It's not a matter of it being disabled, that code is simply
not there.

So I'm not sure what you mean by "master @
de25d9c8c48c7474828e9452184e204b18b8e090".  Your local git tree may
have assigned master to that git commit id, but then it wouldn't have
any metadata_csum support at all.

> I'd rather use debian versions, but metadata_csum is disabled there.
> debian does not sync with git master, so what exactly does it sync
> with?  ie, how are the metadata_csum patches dropped, since they exist
> in master?

See above.  The reason why debian doesn't support metadata_csum is
because it's not ready yet.  If you'd like to help us debug it, we
will be very grateful, but please understand it's still a work in
progress.

There's a big difference between "it mostly works", and "it's ready
for it to be used in production".  When I have time I might drop a
1.43-WIP ("work in progress") into debian experimental, but Debian
Jessie is going to be targetting 3.16, and we will need to make sure
that all of the necessary kernel bits for metadata_csum and
inline_data are working flawlessly before I'll want to let a 1.43
release into Debian testing --- and that's assuming we can get the
1.43 userspace bits fully stablized as well before Jessie date of
November 5, 2014.

Cheers,

					- 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