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>] [day] [month] [year] [list]

Date:	Sat, 9 Aug 2014 00:07:36 -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 11:29:11PM -0400, TR Reardon wrote:
> 
> I meant only: that commit is in master _and_ maint branches, so to get a
> version roughly = 1.42.11 + metadata_csum, I pulled up to that commit.

Right but you gave me the git commit id for 1.42.11, which is not
particularly useful; I know the commit id for v1.42.11 already.  :-)

What I needed to know was the git commit of "master" that you had
grabbed, since the "master" and "next" branches are fairly active
these days.  (The master branch langs the next branch, so depending on
how exciting a life you want to live, you can try the next branch
instead of the master branch.)

> Regardless, the problem exists in kernel too, judging by the JBD2 errors.

Yes, we'll need to look into that.  Definitely worth knowing; thanks
for that.

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