linux-ext4.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Theodore Ts'o <tytso@mit.edu>
To: "Darrick J. Wong" <darrick.wong@oracle.com>
Cc: linux-ext4 <linux-ext4@vger.kernel.org>
Subject: Re: e2fsprogs make check fails
Date: Tue, 5 May 2015 10:11:04 -0400	[thread overview]
Message-ID: <20150505141104.GA12468@thunk.org> (raw)
In-Reply-To: <20150505054818.GI11592@birch.djwong.org>

On Mon, May 04, 2015 at 10:48:18PM -0700, Darrick J. Wong wrote:
> 
> Uhh... I pulled the latest e2fsprogs -next and tried to run 'make check'.
> I think tst_sha256 (and maybe tst_sha512?) need to be pulled out of the
> Makefiles

Oops, sorry, I commented out EXT2FS_SHA256_LENGTH and this caused
tst_sha256 to fail.  I forgot to do a "make clean; make check" pass,
forgetting that the dependencies don't always work for the tst_*
commands.  That's one of those things I should fix...

We are still using sha512 since it's used as part of the password
string-to-key function.

					- Ted

      reply	other threads:[~2015-05-05 14:11 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-05  5:48 e2fsprogs make check fails Darrick J. Wong
2015-05-05 14:11 ` Theodore Ts'o [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20150505141104.GA12468@thunk.org \
    --to=tytso@mit.edu \
    --cc=darrick.wong@oracle.com \
    --cc=linux-ext4@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).