From: "Theodore Ts'o" <tytso@mit.edu>
To: "Darrick J. Wong" <djwong@kernel.org>
Cc: linux-ext4 <linux-ext4@vger.kernel.org>
Subject: Re: e2fsprogs 1.45.7 & 1.46.0?
Date: Tue, 2 Feb 2021 12:20:45 -0500 [thread overview]
Message-ID: <YBmJ7ZIbQP5R1zgo@mit.edu> (raw)
In-Reply-To: <20210202163827.GA7186@magnolia>
On Tue, Feb 02, 2021 at 08:38:27AM -0800, Darrick J. Wong wrote:
> Hi Ted,
>
> So... I see in the e2fsprogs git repo that the release notes and
> version.h that the maint branch is now at 1.45.7 and master is at
> 1.46.0. There's a tag for 1.45.7 but no tag for 1.46.0.
>
> Are those releases official, and did I miss the announcement on the
> list?
Um, sorry, I forgot to push out the tag. I was going to send the
announcement to the list, but got caught up with other things.
One of those things is apparently we have a bug which is causing the
regression test suite to fail on big endian systems, including s390x
and powerpc[1] (although not ppc64el, naturally). I'm working on
getting Harshad access to Debian's porter boxes, so he can debug it
directly. He spotted one bug already (where a le16_to_cpu should have
been le32_to_cpu in e2fsck/journal.c:822), but there is still an
incorrect block bitmap checksum after a fc replay which is causing
j_recover_fast_commit to fail.
[1] https://buildd.debian.org/status/fetch.php?pkg=e2fsprogs&arch=powerpc&ver=1.46.0-1&stamp=1611976060&raw=0
In any case, yes, these releases are official, are up on kernel.org.
I've pushed out the tag for v1.46.0. When we fix the BE fast commit
bug, I'll release e2fsprogs v1.46.1. (There's also a configure script
bug which causes build failures on systems w/o FUSE which is already
fixed in the git tree that will be included in v1.46.1.)
- Ted
prev parent reply other threads:[~2021-02-02 17:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-02 16:38 e2fsprogs 1.45.7 & 1.46.0? Darrick J. Wong
2021-02-02 17:20 ` 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=YBmJ7ZIbQP5R1zgo@mit.edu \
--to=tytso@mit.edu \
--cc=djwong@kernel.org \
--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