From: "Theodore Y. Ts'o" <tytso@mit.edu>
To: Gabriel Krisman Bertazi <krisman@collabora.com>
Cc: kernel@collabora.com, linux-ext4@vger.kernel.org
Subject: Re: [PATCH] ext2fs: Fix build of new superblock fields on BE machines
Date: Wed, 21 Nov 2018 11:24:32 -0500 [thread overview]
Message-ID: <20181121162432.GF26006@thunk.org> (raw)
In-Reply-To: <20181121001127.1868-1-krisman@collabora.com>
On Tue, Nov 20, 2018 at 07:11:27PM -0500, Gabriel Krisman Bertazi wrote:
> New superblock fields must be byte swapped before being accessed in Big
> Endian machines.
>
> Not tested on an actual BE machine.
>
> Signed-off-by: Gabriel Krisman Bertazi <krisman@collabora.com>
> ---
>
> I just noticed this today. I don't see the patch that includes this
> field already pushed to kernel.org, so if you want to squash this one to
> that patch before pushing to make the result more bisectable in BE
> machines, I am ok with that.
Oops, sorry, I just pushed it out before I saw your note. I'll add it
as a follow-on commit right away. Fortunately we don't do too much
debugging on BE machines, so it's probably not worth breaking the git
rules and rewinding, even though it's highly unlikely anyone has done
a git pull in the last 10 minutes or so.
While we're at it, I should have noticed this earler before I acceptd
patch 2 in your series. Could you also send a follow up patch which
adds a quick description of the fname_encoding feature to the ext4.5
man page?
Also, did your v2 patch series to e2fsprogs reflect any of the
comments I made late last night on the rest of the v1 patch series?
Thanks, regards,
- Ted
next prev parent reply other threads:[~2018-11-22 2:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-21 0:11 [PATCH] ext2fs: Fix build of new superblock fields on BE machines Gabriel Krisman Bertazi
2018-11-21 16:24 ` Theodore Y. Ts'o [this message]
2018-11-21 18:27 ` Gabriel Krisman Bertazi
2018-11-21 23:19 ` Theodore Y. 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=20181121162432.GF26006@thunk.org \
--to=tytso@mit.edu \
--cc=kernel@collabora.com \
--cc=krisman@collabora.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;
as well as URLs for NNTP newsgroup(s).