public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Sasha Levin <sashal@kernel.org>
To: Wolfgang Walter <linux@stwm.de>
Cc: Herbert Xu <herbert@gondor.apana.org.au>,
	linux-kernel@vger.kernel.org,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	stable@vger.kernel.org
Subject: Re: 6.18.22: a question to commit "crypto: algif_aead - Revert to operating out-of-place"
Date: Tue, 14 Apr 2026 13:28:17 -0400	[thread overview]
Message-ID: <ad55MXSYo_eZhQX1@laps> (raw)
In-Reply-To: <fe119b5dc5716d1cf4ed53e6420cdf2c@stwm.de>

On Tue, Apr 14, 2026 at 07:04:11PM +0200, Wolfgang Walter wrote:
>Hello
>
>another maybe stupid question to
>
>commit fafe0fa2995a0f7073c1c358d7d3145bcc9aedd8
>Author: Herbert Xu <herbert@gondor.apana.org.au>
>Date:   Thu Mar 26 15:30:20 2026 +0900
>
>    crypto: algif_aead - Revert to operating out-of-place
>
>    [ Upstream commit a664bf3d603dc3bdcf9ae47cc21e0daec706d7a5 ]
>
>    This mostly reverts commit 72548b093ee3 except for the copying of
>    the associated data.
>
>    There is no benefit in operating in-place in algif_aead since the
>    source and destination come from different mappings.  Get rid of
>    all the complexity added for in-place operation and just copy the
>    AD directly.
>
>    Fixes: 72548b093ee3 ("crypto: algif_aead - copy AAD from src to 
>dst")
>    Reported-by: Taeyang Lee <0wn@theori.io>
>    Signed-off-by: Herbert Xu <herbert@gondor.apana.org.au>
>    Signed-off-by: Sasha Levin <sashal@kernel.org>
>
>
>This commit makes
>
>crypto/algif_aead.c
>
>almost like the version in v7.0, but there is a difference:
>
>$ git diff v6.18.22..v7.0 crypto/algif_aead.c
>diff --git a/crypto/algif_aead.c b/crypto/algif_aead.c
>index dda15bb05e89..f8bd45f7dc83 100644
>--- a/crypto/algif_aead.c
>+++ b/crypto/algif_aead.c
>@@ -144,7 +144,7 @@ static int _aead_recvmsg(struct socket *sock, 
>struct msghdr *msg,
>        if (usedpages < outlen) {
>                size_t less = outlen - usedpages;
>
>-               if (used < less) {
>+               if (used < less + (ctx->enc ? 0 : as)) {
>                        err = -EINVAL;
>                        goto free;
>                }
>
>
>Is this intentional? Or is der missing a fix from v7.0 in 6.18.22

This is in 7c1d57841aa0 ("crypto: algif_aead - Fix minimum RX size check for
decryption"). It should make it into the next-next release.

-- 
Thanks,
Sasha

  reply	other threads:[~2026-04-14 17:28 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-11 12:53 Linux 6.18.22 Greg Kroah-Hartman
2026-04-11 12:53 ` Greg Kroah-Hartman
2026-04-14 16:52 ` Regression Linux 6.18.22: ipsec stops working: reason: commit 153d5520c3f9 "crypto: authencesn - Do not place hiseq at end of dst for out-of-place d.cryption" Wolfgang Walter
2026-04-14 16:58   ` Sasha Levin
2026-04-14 17:41     ` Wolfgang Walter
2026-04-14 17:04   ` 6.18.22: a question to commit "crypto: algif_aead - Revert to operating out-of-place" Wolfgang Walter
2026-04-14 17:28     ` Sasha Levin [this message]
2026-04-14 23:39   ` [PATCH] crypto: authencesn - Fix src offset when decrypting in-place Herbert Xu
2026-04-15 19:54     ` Wolfgang Walter

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=ad55MXSYo_eZhQX1@laps \
    --to=sashal@kernel.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=herbert@gondor.apana.org.au \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@stwm.de \
    --cc=stable@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