From: Denis Efremov <efremov@linux.com>
To: linux-crypto@vger.kernel.org
Cc: Denis Efremov <efremov@linux.com>,
Corentin Labbe <clabbe.montjoie@gmail.com>,
Herbert Xu <herbert@gondor.apana.org.au>,
linux-kernel@vger.kernel.org
Subject: [PATCH v2 0/4] crypto: use kfree_sensitive()
Date: Thu, 27 Aug 2020 09:43:58 +0300 [thread overview]
Message-ID: <20200827064402.7130-1-efremov@linux.com> (raw)
kfree_sensitive() is introduced in commit 453431a54934
("mm, treewide: rename kzfree() to kfree_sensitive()") and uses
memzero_explicit() internally. Thus, we can switch to this API
instead of open-coding memzero_explicit() && kfree().
Changes in v2:
- if (op->len) check removed
Denis Efremov (4):
crypto: inside-secure - use kfree_sensitive()
crypto: amlogic - use kfree_sensitive()
crypto: sun8i-ce - use kfree_sensitive()
crypto: sun8i-ss - use kfree_sensitive()
.../crypto/allwinner/sun8i-ce/sun8i-ce-cipher.c | 15 +++------------
.../crypto/allwinner/sun8i-ss/sun8i-ss-cipher.c | 15 +++------------
drivers/crypto/amlogic/amlogic-gxl-cipher.c | 10 ++--------
drivers/crypto/inside-secure/safexcel_hash.c | 3 +--
4 files changed, 9 insertions(+), 34 deletions(-)
--
2.26.2
next reply other threads:[~2020-08-27 6:44 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-27 6:43 Denis Efremov [this message]
2020-08-27 6:43 ` [PATCH v2 1/4] crypto: inside-secure - use kfree_sensitive() Denis Efremov
2020-08-27 14:52 ` Corentin Labbe
2020-09-02 9:02 ` Antoine Tenart
2020-09-02 13:10 ` Van Leeuwen, Pascal
2020-09-04 8:55 ` Denis Efremov
2020-09-04 9:44 ` Van Leeuwen, Pascal
2020-08-27 6:44 ` [PATCH v2 2/4] crypto: amlogic " Denis Efremov
2020-08-27 14:50 ` Corentin Labbe
2020-08-27 6:44 ` [PATCH v2 3/4] crypto: sun8i-ce " Denis Efremov
2020-08-27 14:40 ` Corentin Labbe
2020-08-27 6:44 ` [PATCH v2 4/4] crypto: sun8i-ss " Denis Efremov
2020-08-27 14:41 ` Corentin Labbe
2020-09-04 8:28 ` [PATCH v2 0/4] crypto: " Herbert Xu
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=20200827064402.7130-1-efremov@linux.com \
--to=efremov@linux.com \
--cc=clabbe.montjoie@gmail.com \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.