[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAHk-=wi5GPS3poC_YRy93X38AqkvsFENAviMXHWjgOgo5k7p3g@mail.gmail.com>
Date: Tue, 24 Jan 2023 09:23:56 -0800
From: Linus Torvalds <torvalds@...ux-foundation.org>
To: Sasha Levin <sashal@...nel.org>
Cc: linux-kernel@...r.kernel.org, stable@...r.kernel.org,
kernel test robot <oliver.sang@...el.com>,
Eric Biggers <ebiggers@...nel.org>,
Andreas Dilger <adilger@...ger.ca>,
"Theodore Ts'o" <tytso@....edu>, Jason Donenfeld <Jason@...c4.com>,
Masahiro Yamada <masahiroy@...nel.org>,
adilger.kernel@...ger.ca, linux-ext4@...r.kernel.org
Subject: Re: [PATCH AUTOSEL 6.1 35/35] ext4: deal with legacy signed xattr
name hash values
On Tue, Jan 24, 2023 at 8:50 AM Linus Torvalds
<torvalds@...ux-foundation.org> wrote:
>
> This patch does not work correctly without '-funsigned-char', and I
> don't think that has been back-ported to stable kernels.
>
> That said, the patch *almost* works.
So I'm not convinced this should be back-ported at all, but it's
certainly true that going back and forth between the two cases would
be problematic.
Maybe the right thing to do would be for me to just do that explicit
'unsigned char' even in kernels that don't need it, and also add a
'pr_warn_once()' to make people aware of this case if it ever happens
outside of the xfstests.
So a more complete patch might be something like the attached (which
also changes the polarity of the signed hash test, in order to make
the pr_warn_once() simpler).
Linus
View attachment "patch.diff" of type "text/x-patch" (1026 bytes)
Powered by blists - more mailing lists