public inbox for linux-ext4@vger.kernel.org
 help / color / mirror / Atom feed
From: Brian Foster <bfoster@redhat.com>
To: linux-ext4@vger.kernel.org
Subject: Re: [PATCH] debugfs: byteswap dirsearch dirent buf on big endian systems
Date: Mon, 3 Mar 2025 14:09:05 -0500	[thread overview]
Message-ID: <Z8X-USvFA-ofGrHQ@bfoster> (raw)
In-Reply-To: <20250123135211.575895-1-bfoster@redhat.com>

On Thu, Jan 23, 2025 at 08:52:11AM -0500, Brian Foster wrote:
> fstests test ext4/048 fails on big endian systems due to broken
> debugfs dirsearch functionality. On an s390x system and 4k block
> size, the dirsearch command seems to hang indefinitely. On the same
> system with a 1k block size, the command fails to locate an existing
> entry and causes the test to fail due to unexpected results.
> 
> The cause of the dirsearch failure is lack of byte swapping of the
> on-disk (little endian) dirent buffer before attempting to iterate
> entries in the given block. This leads to garbage record and name
> length values, for example. To resolve this problem, byte swap the
> directory buffer on big endian systems.
> 
> Signed-off-by: Brian Foster <bfoster@redhat.com>
> ---
> 
> Hi all,
> 
> I'm not terribly familiar with this code, but this fixes the test and
> doesn't show any regressions from fstests runs on big or little endian
> systems. Thanks.
> 

Ping... curious if anybody has thoughts on this for dirsearch on big
endian? Thanks!

Brian

> Brian
> 
>  debugfs/htree.c | 6 ++++++
>  1 file changed, 6 insertions(+)
> 
> diff --git a/debugfs/htree.c b/debugfs/htree.c
> index a1008150..4ea8f30b 100644
> --- a/debugfs/htree.c
> +++ b/debugfs/htree.c
> @@ -482,6 +482,12 @@ static int search_dir_block(ext2_filsys fs, blk64_t *blocknr,
>  		return BLOCK_ABORT;
>  	}
>  
> +#ifdef WORDS_BIGENDIAN
> +	errcode = ext2fs_dirent_swab_in(fs, p->buf, 0);
> +	if (errcode)
> +		return BLOCK_ABORT;
> +#endif
> +
>  	while (offset < fs->blocksize) {
>  		dirent = (struct ext2_dir_entry *) (p->buf + offset);
>  		errcode = ext2fs_get_rec_len(fs, dirent, &rec_len);
> -- 
> 2.47.1
> 
> 


  reply	other threads:[~2025-03-03 19:06 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-23 13:52 [PATCH] debugfs: byteswap dirsearch dirent buf on big endian systems Brian Foster
2025-03-03 19:09 ` Brian Foster [this message]
2025-03-04 19:34   ` Darrick J. Wong
2025-05-21 14:51 ` 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=Z8X-USvFA-ofGrHQ@bfoster \
    --to=bfoster@redhat.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