linux-ext4.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ted Ts'o <tytso@mit.edu>
To: Eric Sandeen <sandeen@redhat.com>
Cc: ext4 development <linux-ext4@vger.kernel.org>
Subject: Re: e2fsprogs 1.42-WIP busted on big endian
Date: Tue, 8 Nov 2011 15:28:09 -0500	[thread overview]
Message-ID: <20111108202809.GO24234@thunk.org> (raw)
In-Reply-To: <4EB958E5.3080604@redhat.com>

On Tue, Nov 08, 2011 at 10:29:25AM -0600, Eric Sandeen wrote:
> This was noted in commit ccc7cf032852dd5c84b227bafb481b1d158e2b5e:
> 
> 
> commit ccc7cf032852dd5c84b227bafb481b1d158e2b5e
> Author: Theodore Ts'o <tytso@mit.edu>
> Date:   Fri Jul 30 18:41:47 2010 -0400
> 
>     libext2fs: fix obvious big-endian bugs introduced by 64-bit changes
>     
>     These patches fix obvious bone-headed mistakes, so e2fsprogs will now
>     build and mostly work on powerpc.  The m_meta_bg, u_mke2fs, and
>     u_tune2fs tests are still failing, however, so there's still work to do...
>     
>     Signed-off-by: "Theodore Ts'o" <tytso@mit.edu>
> 
> but not fixed yet.  Just a heads up, when contemplating a 1.42
> release.  I will try to find some time to look into it, but it's not
> a simple regression, something must have gone wrong in the bowls of
> 64-bitness.

Um, thanks for reminding me!  I'll try to schedule time to look at
them later in this week, but if you get a chance ahead of me, let me
know if you make any progress.

One of the other things on my todo list is I noticed that apparently I
accidently broke the shared library ABI for the e2tools package, and
I need to figure out what I need to fix up so that e2tools doesn't
have to be recompiled.

						- Ted

       

  reply	other threads:[~2011-11-08 20:28 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-08 16:29 e2fsprogs 1.42-WIP busted on big endian Eric Sandeen
2011-11-08 20:28 ` Ted Ts'o [this message]
2011-11-08 22:27   ` Eric Sandeen

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=20111108202809.GO24234@thunk.org \
    --to=tytso@mit.edu \
    --cc=linux-ext4@vger.kernel.org \
    --cc=sandeen@redhat.com \
    /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).