From: Eric Biggers <ebiggers@kernel.org>
To: Sasha Levin <sashal@kernel.org>
Cc: stable@vger.kernel.org, Herbert Xu <herbert@gondor.apana.org.au>,
linux-crypto@vger.kernel.org, netdev@vger.kernel.org,
Steffen Klassert <steffen.klassert@secunet.com>
Subject: Re: [PATCH 5.10.y 1/3] net: ipv4: stop checking crypto_ahash_alignmask
Date: Wed, 13 May 2026 10:51:22 -0700 [thread overview]
Message-ID: <20260513175122.GC2128@quark> (raw)
In-Reply-To: <20260513171555.3876989-1-sashal@kernel.org>
[+Cc linux-crypto@vger.kernel.org, netdev@vger.kernel.org,
Steffen Klassert <steffen.klassert@secunet.com> ]
On Wed, May 13, 2026 at 01:15:52PM -0400, Sasha Levin wrote:
> From: Eric Biggers <ebiggers@google.com>
>
> [ Upstream commit e77f5dd701381cef35b9ea8b6dea6e62c8a7f9f3 ]
>
> Now that the alignmask for ahash and shash algorithms is always 0,
> crypto_ahash_alignmask() always returns 0 and will be removed. In
> preparation for this, stop checking crypto_ahash_alignmask() in ah4.c.
>
> Signed-off-by: Eric Biggers <ebiggers@google.com>
> Signed-off-by: Herbert Xu <herbert@gondor.apana.org.au>
> Stable-dep-of: ec54093e6a8f ("xfrm: ah: account for ESN high bits in async callbacks")
> Signed-off-by: Sasha Levin <sashal@kernel.org>
You forgot to send this to the IPsec maintainers, linux-crypto, and
netdev. See Documentation/process/submitting-patches.rst for some tips
on how to use scripts/get_maintainer.pl to find the right place to send
kernel patches.
This commit was part of the series
https://lore.kernel.org/linux-crypto/20231022081100.123613-1-ebiggers@kernel.org/
What is your rationale for why it's safe to backport this patch 18 of a
30-patch series by itself? "The alignmask for ahash and shash
algorithms is always 0" is definitely *not* true in older kernels.
I *think* it's probably okay. I think this would just regress AH
performance in some cases, and "no one" uses AH anyway.
Just keep in mind this is effectively new development, which needs
review like any other kernel patch. Not even Cc'ing the subsystem
mailing lists isn't a great approach.
- Eric
prev parent reply other threads:[~2026-05-13 17:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-12 12:39 FAILED: patch "[PATCH] xfrm: ah: account for ESN high bits in async callbacks" failed to apply to 5.10-stable tree gregkh
2026-05-13 17:15 ` [PATCH 5.10.y 1/3] net: ipv4: stop checking crypto_ahash_alignmask Sasha Levin
2026-05-13 17:15 ` [PATCH 5.10.y 2/3] net: ipv6: " Sasha Levin
2026-05-13 17:15 ` [PATCH 5.10.y 3/3] xfrm: ah: account for ESN high bits in async callbacks Sasha Levin
2026-05-13 17:51 ` Eric Biggers [this message]
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=20260513175122.GC2128@quark \
--to=ebiggers@kernel.org \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=sashal@kernel.org \
--cc=stable@vger.kernel.org \
--cc=steffen.klassert@secunet.com \
/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