From: Eric Whitney <enwlinux@gmail.com>
To: sandeen@redhat.com
Cc: linux-ext4@vger.kernel.org
Subject: Re: Release of e2fsprogs 1.43.5
Date: Thu, 10 Aug 2017 13:30:44 -0400 [thread overview]
Message-ID: <20170810173044.GA16896@localhost.localdomain> (raw)
In-Reply-To: <552dd796-7ba5-6a10-b9fd-0d1a2aa07041@redhat.com>
* Eric Sandeen <esandeen@redhat.com>:
> On 8/5/17 9:34 AM, Theodore Ts'o wrote:
> > I've released e2fsprogs 1.43.5 in all of the usual places; it's tagged
> > in the git trees on git.kernel.org, github, and sourceforge, and
> > available for download at:
> >
> > ftp://ftp.kernel.org/pub/linux/kernel/people/tytso/e2fsprogs/v1.43.5
> >
> > and
> >
> > http://prdownloads.sourceforge.net/e2fsprogs/e2fsprogs-1.43.5.tar.gz
> >
> > The release notes for 1.43.5 can be found below.
>
> I'm getting test failures in rawhide with this, FWIW; on i686
> and arm:
>
> 336 tests succeeded 3 tests failed
> Tests failed: f_del_dup_quota f_quota f_quota_extent_opt
>
> Haven't dug into this yet (failures are on ephemeral build root
> on a build host), but has anyone else seen problems?
>
Yes - I can reproduce these failures on Debian Jessie on 32 bit x86, as can
Ted.
Reverting "libext2fs: fix compile errors/warnings" (a850bc56e0aa) resolves
the problem for me. In particular, undoing the format string changes in
scan_dquots_callback() fixes the failures. I think we need to use %lld as
dqb_curspace and dqb_curinodes are __le64, as addressed in "e2fsck: fix type
mismatches in quota warning message" (f09669fc6889).
Eric
next prev parent reply other threads:[~2017-08-10 17:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-05 16:34 Release of e2fsprogs 1.43.5 Theodore Ts'o
2017-08-09 23:58 ` Eric Sandeen
2017-08-10 17:30 ` Eric Whitney [this message]
2017-08-10 17:37 ` Darrick J. Wong
2017-08-11 21:23 ` Eric Whitney
2017-08-13 19:20 ` [PATCH] libsupport: fix 32-bit quota test failures Theodore Ts'o
2017-08-10 18:05 ` Release of e2fsprogs 1.43.5 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=20170810173044.GA16896@localhost.localdomain \
--to=enwlinux@gmail.com \
--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).