From: Sasha Levin <sashal@kernel.org>
To: stable@vger.kernel.org
Cc: Sasha Levin <sashal@kernel.org>,
linux-crypto@vger.kernel.org, linux-kernel@vger.kernel.org,
Eric Biggers <ebiggers@kernel.org>, Taeyang Lee <0wn@theori.io>,
Feng Ning <feng@innora.ai>,
Demi Marie Obenour <demiobenour@gmail.com>,
Herbert Xu <herbert@gondor.apana.org.au>
Subject: Re: [PATCH 6.1] crypto: af_alg - Remove zero-copy support from skcipher and aead
Date: Sun, 19 Jul 2026 11:00:27 -0400 [thread overview]
Message-ID: <20260718192718.0013-stable-reply@kernel.org> (raw)
In-Reply-To: <20260717033312.285557-1-ebiggers@kernel.org>
> The zero-copy support is one of the riskiest aspects of AF_ALG. It
> allows userspace to request cryptographic operations directly on
> pagecache pages of files like the 'su' binary.
Queued for 6.1, thanks.
--
Thanks,
Sasha
prev parent reply other threads:[~2026-07-19 15:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-17 3:33 [PATCH 6.1] crypto: af_alg - Remove zero-copy support from skcipher and aead Eric Biggers
2026-07-19 15:00 ` Sasha Levin [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=20260718192718.0013-stable-reply@kernel.org \
--to=sashal@kernel.org \
--cc=0wn@theori.io \
--cc=demiobenour@gmail.com \
--cc=ebiggers@kernel.org \
--cc=feng@innora.ai \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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