From: "Darrick J. Wong" <djwong@kernel.org>
To: Theodore Ts'o <tytso@mit.edu>
Cc: Ext4 Developers List <linux-ext4@vger.kernel.org>
Subject: Re: Release candidate for e2fsprogs 1.47.2 is available
Date: Sat, 30 Nov 2024 12:36:07 -0800 [thread overview]
Message-ID: <20241130203607.GC9417@frogsfrogsfrogs> (raw)
In-Reply-To: <20241130013429.GA812025@mit.edu>
On Fri, Nov 29, 2024 at 08:34:29PM -0500, Theodore Ts'o wrote:
> Hi all,
>
> There is a release candidate for e2fsprogs 1.47.2 available at:
>
> https://www.kernel.org/pub/linux/kernel/people/tytso/e2fsprogs/testing/v1.47.2-rc1/e2fsprogs-1.47.2-rc1.tar.gz
>
> It is also uploaded to Debian unstable, for folks who want to try that out.
>
> A known issue is that f_clear_orphan_file is failing on s390x,
> powerpc, and ppc64 which is why Debian packages haven't been built on
> those architectures:
>
> https://buildd.debian.org/status/package.php?p=e2fsprogs
IOWs, the big endian architectures.
Hmmm, why does ext2fs_do_orphan_file_block_csum claim to return a __u32
yet the actual return statement returns an __le32:
return ext2fs_cpu_to_le32(crc);
Particularly because ext2fs_orphan_file_block_csum_verify then compares
the returned __le32 value to a __u32 that was converted from the ondisk
structure:
return ext2fs_le32_to_cpu(tail->ob_checksum) == crc;
AFAICT ext2fs_do_orphan_file_block_csum should not do that conversion,
and mkorphan_proc should be doing:
tail->ob_checksum = cpu_to_le32(
ext2fs_do_orphan_file_block_csum(...));
But I'm not that familiar with this code.
--D
> Please give it a try, and let me know if you run into any other
> problems.
>
> Many thanks!!
>
> - Ted
>
next prev parent reply other threads:[~2024-11-30 20:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-30 1:34 Release candidate for e2fsprogs 1.47.2 is available Theodore Ts'o
2024-11-30 20:36 ` Darrick J. Wong [this message]
2024-11-30 22:42 ` Theodore Ts'o
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=20241130203607.GC9417@frogsfrogsfrogs \
--to=djwong@kernel.org \
--cc=linux-ext4@vger.kernel.org \
--cc=tytso@mit.edu \
/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