From: Eric Biggers <ebiggers@kernel.org>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: stable@vger.kernel.org, patches@lists.linux.dev,
Jiri Slaby <jslaby@suse.cz>, Borislav Petkov <bp@suse.de>,
"David S. Miller" <davem@davemloft.net>,
Herbert Xu <herbert@gondor.apana.org.au>,
"H. Peter Anvin" <hpa@zytor.com>, Ingo Molnar <mingo@redhat.com>,
linux-arch@vger.kernel.org, linux-crypto@vger.kernel.org,
Thomas Gleixner <tglx@linutronix.de>, x86-ml <x86@kernel.org>,
Sasha Levin <sashal@kernel.org>
Subject: Re: [PATCH 5.4 243/321] x86/asm/crypto: Annotate local functions
Date: Thu, 12 Dec 2024 18:08:56 +0000 [thread overview]
Message-ID: <20241212180856.GB112010@google.com> (raw)
In-Reply-To: <2024121201-recoup-gumming-92ce@gregkh>
On Thu, Dec 12, 2024 at 07:05:24PM +0100, Greg Kroah-Hartman wrote:
> On Thu, Dec 12, 2024 at 06:00:23PM +0000, Eric Biggers wrote:
> > On Thu, Dec 12, 2024 at 04:02:41PM +0100, Greg Kroah-Hartman wrote:
> > > 5.4-stable review patch. If anyone has any objections, please let me know.
> > >
> > > ------------------
> > >
> > > From: Jiri Slaby <jslaby@suse.cz>
> > >
> > > [ Upstream commit 74d8b90a889022e306b543ff2147a6941c99b354 ]
> > >
> > > Use the newly added SYM_FUNC_START_LOCAL to annotate beginnings of all
> > > functions which do not have ".globl" annotation, but their endings are
> > > annotated by ENDPROC. This is needed to balance ENDPROC for tools that
> > > generate debuginfo.
> > >
> > > These function names are not prepended with ".L" as they might appear in
> > > call traces and they wouldn't be visible after such change.
> > >
> > > To be symmetric, the functions' ENDPROCs are converted to the new
> > > SYM_FUNC_END.
> > >
> > > Signed-off-by: Jiri Slaby <jslaby@suse.cz>
> > > Signed-off-by: Borislav Petkov <bp@suse.de>
> > > Cc: "David S. Miller" <davem@davemloft.net>
> > > Cc: Herbert Xu <herbert@gondor.apana.org.au>
> > > Cc: "H. Peter Anvin" <hpa@zytor.com>
> > > Cc: Ingo Molnar <mingo@redhat.com>
> > > Cc: linux-arch@vger.kernel.org
> > > Cc: linux-crypto@vger.kernel.org
> > > Cc: Thomas Gleixner <tglx@linutronix.de>
> > > Cc: x86-ml <x86@kernel.org>
> > > Link: https://lkml.kernel.org/r/20191011115108.12392-7-jslaby@suse.cz
> > > Stable-dep-of: 3b2f2d22fb42 ("crypto: x86/aegis128 - access 32-bit arguments as 32-bit")
> > > Signed-off-by: Sasha Levin <sashal@kernel.org>
> > > ---
> > > arch/x86/crypto/aegis128-aesni-asm.S | 8 ++--
> > > arch/x86/crypto/aesni-intel_asm.S | 49 ++++++++------------
> > > arch/x86/crypto/camellia-aesni-avx-asm_64.S | 20 ++++----
> > > arch/x86/crypto/camellia-aesni-avx2-asm_64.S | 20 ++++----
> > > arch/x86/crypto/cast5-avx-x86_64-asm_64.S | 8 ++--
> > > arch/x86/crypto/cast6-avx-x86_64-asm_64.S | 8 ++--
> > > arch/x86/crypto/chacha-ssse3-x86_64.S | 4 +-
> > > arch/x86/crypto/ghash-clmulni-intel_asm.S | 4 +-
> > > arch/x86/crypto/serpent-avx-x86_64-asm_64.S | 8 ++--
> > > arch/x86/crypto/serpent-avx2-asm_64.S | 8 ++--
> > > arch/x86/crypto/twofish-avx-x86_64-asm_64.S | 8 ++--
> > > 11 files changed, 68 insertions(+), 77 deletions(-)
> >
> > Unless the author of this patch acks this I'd rather you skipped this. It's not
> > worth the risk of regressions in the crypto code.
>
> It's a dependancy of commit 3b2f2d22fb42 ("crypto: x86/aegis128 - access
> 32-bit arguments as 32-bit"), so should we drop that one also?
>
Well it is not a dependency if the conflict is properly resolved, but I would
just drop it too. In theory it fixes a bug, but we haven't seen gcc or clang
generating code that makes it matter. Also I've noticed that some other asm
files have the same issue...
- Eric
next prev parent reply other threads:[~2024-12-12 18:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20241212144229.291682835@linuxfoundation.org>
2024-12-12 15:02 ` [PATCH 5.4 243/321] x86/asm/crypto: Annotate local functions Greg Kroah-Hartman
2024-12-12 18:00 ` Eric Biggers
2024-12-12 18:05 ` Greg Kroah-Hartman
2024-12-12 18:08 ` Eric Biggers [this message]
2024-12-13 12:14 ` Greg Kroah-Hartman
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=20241212180856.GB112010@google.com \
--to=ebiggers@kernel.org \
--cc=bp@suse.de \
--cc=davem@davemloft.net \
--cc=gregkh@linuxfoundation.org \
--cc=herbert@gondor.apana.org.au \
--cc=hpa@zytor.com \
--cc=jslaby@suse.cz \
--cc=linux-arch@vger.kernel.org \
--cc=linux-crypto@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=patches@lists.linux.dev \
--cc=sashal@kernel.org \
--cc=stable@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=x86@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