From: Eric Biggers <ebiggers@kernel.org>
To: linux-crypto@vger.kernel.org, Herbert Xu <herbert@gondor.apana.org.au>
Cc: linux-kernel@vger.kernel.org, linux-hardening@vger.kernel.org,
Taeyang Lee <0wn@theori.io>, Brian Pak <bpak@theori.io>,
Juno Im <juno@theori.io>, Jungwon Lim <setuid0@theori.io>,
Tim Becker <tjbecker@theori.io>,
Demi Marie Obenour <demiobenour@gmail.com>,
Feng Ning <feng@innora.ai>,
stable@vger.kernel.org
Subject: Re: [PATCH v2] crypto: af_alg - Remove zero-copy support from AF_ALG
Date: Mon, 4 May 2026 02:24:42 -0700 [thread overview]
Message-ID: <20260504092442.GA2486@quark> (raw)
In-Reply-To: <20260504071025.180058-1-ebiggers@kernel.org>
On Mon, May 04, 2026 at 12:10:25AM -0700, Eric Biggers wrote:
> Thus, the risks of the zero-copy support in AF_ALG vastly outweigh its
> benefits. Just remove it.
I realized that the "hash" algorithm type still does zero-copy even
after this patch. I.e. this patch affects only "skcipher" and "aead".
Those are the more important ones, but we should do "hash" too.
The diff is still fine, but I'll adjust the patch description to clarify
the scope, and send a separate patch to handle "hash".
- Eric
next prev parent reply other threads:[~2026-05-04 9:24 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-04 6:15 [PATCH] crypto: af_alg - Remove zero-copy support from AF_ALG Eric Biggers
2026-05-04 6:54 ` Demi Marie Obenour
2026-05-04 6:56 ` Eric Biggers
2026-05-04 6:59 ` Demi Marie Obenour
2026-05-04 7:07 ` Eric Biggers
2026-05-04 7:10 ` [PATCH v2] " Eric Biggers
2026-05-04 9:24 ` Eric Biggers [this message]
2026-05-04 22:53 ` [PATCH v3] crypto: af_alg - Remove zero-copy support from skcipher and aead Eric Biggers
2026-05-04 16:07 ` [PATCH] crypto: af_alg - Remove zero-copy support from AF_ALG Ⓐlï P☮latel
2026-05-04 17:47 ` Eric Biggers
2026-05-04 18:26 ` Ⓐlï P☮latel
2026-05-04 22:25 ` Eric Biggers
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=20260504092442.GA2486@quark \
--to=ebiggers@kernel.org \
--cc=0wn@theori.io \
--cc=bpak@theori.io \
--cc=demiobenour@gmail.com \
--cc=feng@innora.ai \
--cc=herbert@gondor.apana.org.au \
--cc=juno@theori.io \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-hardening@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=setuid0@theori.io \
--cc=stable@vger.kernel.org \
--cc=tjbecker@theori.io \
/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