2019-05-29 16:57:49 -07:00
|
|
|
// SPDX-License-Identifier: GPL-2.0-only
|
2011-09-26 22:23:50 -07:00
|
|
|
/*
|
|
|
|
* Crypto user configuration API.
|
|
|
|
*
|
|
|
|
* Copyright (C) 2011 secunet Security Networks AG
|
|
|
|
* Copyright (C) 2011 Steffen Klassert <steffen.klassert@secunet.com>
|
|
|
|
*/
|
|
|
|
|
|
|
|
#include <linux/module.h>
|
|
|
|
#include <linux/crypto.h>
|
|
|
|
#include <linux/cryptouser.h>
|
2012-03-29 00:03:47 -07:00
|
|
|
#include <linux/sched.h>
|
2011-09-26 22:23:50 -07:00
|
|
|
#include <linux/security.h>
|
2019-07-09 04:11:24 -07:00
|
|
|
#include <net/netlink.h>
|
2011-09-26 22:23:50 -07:00
|
|
|
#include <net/net_namespace.h>
|
2019-07-09 04:11:24 -07:00
|
|
|
#include <net/sock.h>
|
2012-03-29 00:03:47 -07:00
|
|
|
#include <crypto/internal/skcipher.h>
|
2015-06-21 04:11:45 -07:00
|
|
|
#include <crypto/internal/rng.h>
|
2015-06-16 10:30:55 -07:00
|
|
|
#include <crypto/akcipher.h>
|
2016-06-22 09:49:13 -07:00
|
|
|
#include <crypto/kpp.h>
|
2012-03-29 00:03:47 -07:00
|
|
|
|
2011-09-26 22:23:50 -07:00
|
|
|
#include "internal.h"
|
|
|
|
|
2013-02-05 10:19:15 -07:00
|
|
|
#define null_terminated(x) (strnlen(x, sizeof(x)) < sizeof(x))
|
|
|
|
|
2012-08-28 06:46:54 -07:00
|
|
|
static DEFINE_MUTEX(crypto_cfg_mutex);
|
2011-09-26 22:23:50 -07:00
|
|
|
|
|
|
|
struct crypto_dump_info {
|
|
|
|
struct sk_buff *in_skb;
|
|
|
|
struct sk_buff *out_skb;
|
|
|
|
u32 nlmsg_seq;
|
|
|
|
u16 nlmsg_flags;
|
|
|
|
};
|
|
|
|
|
crypto: remove CONFIG_CRYPTO_STATS
Remove support for the "Crypto usage statistics" feature
(CONFIG_CRYPTO_STATS). This feature does not appear to have ever been
used, and it is harmful because it significantly reduces performance and
is a large maintenance burden.
Covering each of these points in detail:
1. Feature is not being used
Since these generic crypto statistics are only readable using netlink,
it's fairly straightforward to look for programs that use them. I'm
unable to find any evidence that any such programs exist. For example,
Debian Code Search returns no hits except the kernel header and kernel
code itself and translations of the kernel header:
https://codesearch.debian.net/search?q=CRYPTOCFGA_STAT&literal=1&perpkg=1
The patch series that added this feature in 2018
(https://lore.kernel.org/linux-crypto/1537351855-16618-1-git-send-email-clabbe@baylibre.com/)
said "The goal is to have an ifconfig for crypto device." This doesn't
appear to have happened.
It's not clear that there is real demand for crypto statistics. Just
because the kernel provides other types of statistics such as I/O and
networking statistics and some people find those useful does not mean
that crypto statistics are useful too.
Further evidence that programs are not using CONFIG_CRYPTO_STATS is that
it was able to be disabled in RHEL and Fedora as a bug fix
(https://gitlab.com/redhat/centos-stream/src/kernel/centos-stream-9/-/merge_requests/2947).
Even further evidence comes from the fact that there are and have been
bugs in how the stats work, but they were never reported. For example,
before Linux v6.7 hash stats were double-counted in most cases.
There has also never been any documentation for this feature, so it
might be hard to use even if someone wanted to.
2. CONFIG_CRYPTO_STATS significantly reduces performance
Enabling CONFIG_CRYPTO_STATS significantly reduces the performance of
the crypto API, even if no program ever retrieves the statistics. This
primarily affects systems with a large number of CPUs. For example,
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2039576 reported
that Lustre client encryption performance improved from 21.7GB/s to
48.2GB/s by disabling CONFIG_CRYPTO_STATS.
It can be argued that this means that CONFIG_CRYPTO_STATS should be
optimized with per-cpu counters similar to many of the networking
counters. But no one has done this in 5+ years. This is consistent
with the fact that the feature appears to be unused, so there seems to
be little interest in improving it as opposed to just disabling it.
It can be argued that because CONFIG_CRYPTO_STATS is off by default,
performance doesn't matter. But Linux distros tend to error on the side
of enabling options. The option is enabled in Ubuntu and Arch Linux,
and until recently was enabled in RHEL and Fedora (see above). So, even
just having the option available is harmful to users.
3. CONFIG_CRYPTO_STATS is a large maintenance burden
There are over 1000 lines of code associated with CONFIG_CRYPTO_STATS,
spread among 32 files. It significantly complicates much of the
implementation of the crypto API. After the initial submission, many
fixes and refactorings have consumed effort of multiple people to keep
this feature "working". We should be spending this effort elsewhere.
Acked-by: Ard Biesheuvel <ardb@kernel.org>
Acked-by: Corentin Labbe <clabbe@baylibre.com>
Signed-off-by: Eric Biggers <ebiggers@google.com>
Signed-off-by: Herbert Xu <herbert@gondor.apana.org.au>
2024-03-12 20:48:21 -07:00
|
|
|
static struct crypto_alg *crypto_alg_match(struct crypto_user_alg *p, int exact)
|
2011-09-26 22:23:50 -07:00
|
|
|
{
|
|
|
|
struct crypto_alg *q, *alg = NULL;
|
|
|
|
|
|
|
|
down_read(&crypto_alg_sem);
|
|
|
|
|
|
|
|
list_for_each_entry(q, &crypto_alg_list, cra_list) {
|
2011-10-21 05:37:10 -07:00
|
|
|
int match = 0;
|
2011-09-26 22:23:50 -07:00
|
|
|
|
2019-07-02 14:17:00 -07:00
|
|
|
if (crypto_is_larval(q))
|
|
|
|
continue;
|
|
|
|
|
2011-09-26 22:23:50 -07:00
|
|
|
if ((q->cra_flags ^ p->cru_type) & p->cru_mask)
|
|
|
|
continue;
|
|
|
|
|
|
|
|
if (strlen(p->cru_driver_name))
|
|
|
|
match = !strcmp(q->cra_driver_name,
|
|
|
|
p->cru_driver_name);
|
|
|
|
else if (!exact)
|
|
|
|
match = !strcmp(q->cra_name, p->cru_name);
|
|
|
|
|
2015-04-07 06:27:01 -07:00
|
|
|
if (!match)
|
|
|
|
continue;
|
|
|
|
|
|
|
|
if (unlikely(!crypto_mod_get(q)))
|
|
|
|
continue;
|
|
|
|
|
|
|
|
alg = q;
|
|
|
|
break;
|
2011-09-26 22:23:50 -07:00
|
|
|
}
|
|
|
|
|
|
|
|
up_read(&crypto_alg_sem);
|
|
|
|
|
|
|
|
return alg;
|
|
|
|
}
|
|
|
|
|
2011-09-26 22:48:01 -07:00
|
|
|
static int crypto_report_cipher(struct sk_buff *skb, struct crypto_alg *alg)
|
|
|
|
{
|
|
|
|
struct crypto_report_cipher rcipher;
|
|
|
|
|
2018-11-03 14:56:03 -07:00
|
|
|
memset(&rcipher, 0, sizeof(rcipher));
|
|
|
|
|
|
|
|
strscpy(rcipher.type, "cipher", sizeof(rcipher.type));
|
2011-09-26 22:48:01 -07:00
|
|
|
|
|
|
|
rcipher.blocksize = alg->cra_blocksize;
|
|
|
|
rcipher.min_keysize = alg->cra_cipher.cia_min_keysize;
|
|
|
|
rcipher.max_keysize = alg->cra_cipher.cia_max_keysize;
|
|
|
|
|
2018-11-03 14:56:03 -07:00
|
|
|
return nla_put(skb, CRYPTOCFGA_REPORT_CIPHER,
|
|
|
|
sizeof(rcipher), &rcipher);
|
2011-09-26 22:48:01 -07:00
|
|
|
}
|
|
|
|
|
2011-09-26 22:48:48 -07:00
|
|
|
static int crypto_report_comp(struct sk_buff *skb, struct crypto_alg *alg)
|
|
|
|
{
|
|
|
|
struct crypto_report_comp rcomp;
|
|
|
|
|
2018-11-03 14:56:03 -07:00
|
|
|
memset(&rcomp, 0, sizeof(rcomp));
|
|
|
|
|
|
|
|
strscpy(rcomp.type, "compression", sizeof(rcomp.type));
|
2011-09-26 22:48:48 -07:00
|
|
|
|
2018-11-03 14:56:03 -07:00
|
|
|
return nla_put(skb, CRYPTOCFGA_REPORT_COMPRESS, sizeof(rcomp), &rcomp);
|
2011-09-26 22:48:48 -07:00
|
|
|
}
|
|
|
|
|
2011-09-26 22:23:50 -07:00
|
|
|
static int crypto_report_one(struct crypto_alg *alg,
|
|
|
|
struct crypto_user_alg *ualg, struct sk_buff *skb)
|
|
|
|
{
|
2018-11-03 14:56:03 -07:00
|
|
|
memset(ualg, 0, sizeof(*ualg));
|
|
|
|
|
|
|
|
strscpy(ualg->cru_name, alg->cra_name, sizeof(ualg->cru_name));
|
|
|
|
strscpy(ualg->cru_driver_name, alg->cra_driver_name,
|
2013-02-05 10:19:13 -07:00
|
|
|
sizeof(ualg->cru_driver_name));
|
2018-11-03 14:56:03 -07:00
|
|
|
strscpy(ualg->cru_module_name, module_name(alg->cra_module),
|
2013-02-05 10:19:13 -07:00
|
|
|
sizeof(ualg->cru_module_name));
|
|
|
|
|
|
|
|
ualg->cru_type = 0;
|
|
|
|
ualg->cru_mask = 0;
|
2011-09-26 22:23:50 -07:00
|
|
|
ualg->cru_flags = alg->cra_flags;
|
2017-12-29 09:00:46 -07:00
|
|
|
ualg->cru_refcnt = refcount_read(&alg->cra_refcnt);
|
2011-09-26 22:23:50 -07:00
|
|
|
|
2012-04-01 17:19:05 -07:00
|
|
|
if (nla_put_u32(skb, CRYPTOCFGA_PRIORITY_VAL, alg->cra_priority))
|
|
|
|
goto nla_put_failure;
|
2011-09-26 22:25:05 -07:00
|
|
|
if (alg->cra_flags & CRYPTO_ALG_LARVAL) {
|
|
|
|
struct crypto_report_larval rl;
|
|
|
|
|
2018-11-03 14:56:03 -07:00
|
|
|
memset(&rl, 0, sizeof(rl));
|
|
|
|
strscpy(rl.type, "larval", sizeof(rl.type));
|
|
|
|
if (nla_put(skb, CRYPTOCFGA_REPORT_LARVAL, sizeof(rl), &rl))
|
2012-04-01 17:19:05 -07:00
|
|
|
goto nla_put_failure;
|
2011-09-26 22:25:05 -07:00
|
|
|
goto out;
|
|
|
|
}
|
|
|
|
|
2011-09-26 22:24:29 -07:00
|
|
|
if (alg->cra_type && alg->cra_type->report) {
|
|
|
|
if (alg->cra_type->report(skb, alg))
|
|
|
|
goto nla_put_failure;
|
2011-09-26 22:48:01 -07:00
|
|
|
|
|
|
|
goto out;
|
|
|
|
}
|
|
|
|
|
|
|
|
switch (alg->cra_flags & (CRYPTO_ALG_TYPE_MASK | CRYPTO_ALG_LARVAL)) {
|
|
|
|
case CRYPTO_ALG_TYPE_CIPHER:
|
|
|
|
if (crypto_report_cipher(skb, alg))
|
|
|
|
goto nla_put_failure;
|
|
|
|
|
2011-09-26 22:48:48 -07:00
|
|
|
break;
|
|
|
|
case CRYPTO_ALG_TYPE_COMPRESS:
|
|
|
|
if (crypto_report_comp(skb, alg))
|
|
|
|
goto nla_put_failure;
|
|
|
|
|
2011-09-26 22:48:01 -07:00
|
|
|
break;
|
2011-09-26 22:24:29 -07:00
|
|
|
}
|
|
|
|
|
2011-09-26 22:25:05 -07:00
|
|
|
out:
|
2011-09-26 22:23:50 -07:00
|
|
|
return 0;
|
|
|
|
|
|
|
|
nla_put_failure:
|
|
|
|
return -EMSGSIZE;
|
|
|
|
}
|
|
|
|
|
|
|
|
static int crypto_report_alg(struct crypto_alg *alg,
|
|
|
|
struct crypto_dump_info *info)
|
|
|
|
{
|
|
|
|
struct sk_buff *in_skb = info->in_skb;
|
|
|
|
struct sk_buff *skb = info->out_skb;
|
|
|
|
struct nlmsghdr *nlh;
|
|
|
|
struct crypto_user_alg *ualg;
|
|
|
|
int err = 0;
|
|
|
|
|
2012-09-07 13:12:54 -07:00
|
|
|
nlh = nlmsg_put(skb, NETLINK_CB(in_skb).portid, info->nlmsg_seq,
|
2011-09-26 22:23:50 -07:00
|
|
|
CRYPTO_MSG_GETALG, sizeof(*ualg), info->nlmsg_flags);
|
|
|
|
if (!nlh) {
|
|
|
|
err = -EMSGSIZE;
|
|
|
|
goto out;
|
|
|
|
}
|
|
|
|
|
|
|
|
ualg = nlmsg_data(nlh);
|
|
|
|
|
|
|
|
err = crypto_report_one(alg, ualg, skb);
|
|
|
|
if (err) {
|
|
|
|
nlmsg_cancel(skb, nlh);
|
|
|
|
goto out;
|
|
|
|
}
|
|
|
|
|
|
|
|
nlmsg_end(skb, nlh);
|
|
|
|
|
|
|
|
out:
|
|
|
|
return err;
|
|
|
|
}
|
|
|
|
|
|
|
|
static int crypto_report(struct sk_buff *in_skb, struct nlmsghdr *in_nlh,
|
|
|
|
struct nlattr **attrs)
|
|
|
|
{
|
2019-07-09 04:11:24 -07:00
|
|
|
struct net *net = sock_net(in_skb->sk);
|
2011-09-26 22:23:50 -07:00
|
|
|
struct crypto_user_alg *p = nlmsg_data(in_nlh);
|
|
|
|
struct crypto_alg *alg;
|
|
|
|
struct sk_buff *skb;
|
|
|
|
struct crypto_dump_info info;
|
|
|
|
int err;
|
|
|
|
|
2013-02-05 10:19:15 -07:00
|
|
|
if (!null_terminated(p->cru_name) || !null_terminated(p->cru_driver_name))
|
|
|
|
return -EINVAL;
|
|
|
|
|
2014-11-19 21:44:32 -07:00
|
|
|
alg = crypto_alg_match(p, 0);
|
2011-09-26 22:23:50 -07:00
|
|
|
if (!alg)
|
|
|
|
return -ENOENT;
|
|
|
|
|
2015-04-07 06:27:01 -07:00
|
|
|
err = -ENOMEM;
|
2018-01-25 03:06:02 -07:00
|
|
|
skb = nlmsg_new(NLMSG_DEFAULT_SIZE, GFP_KERNEL);
|
2011-09-26 22:23:50 -07:00
|
|
|
if (!skb)
|
2015-04-07 06:27:01 -07:00
|
|
|
goto drop_alg;
|
2011-09-26 22:23:50 -07:00
|
|
|
|
|
|
|
info.in_skb = in_skb;
|
|
|
|
info.out_skb = skb;
|
|
|
|
info.nlmsg_seq = in_nlh->nlmsg_seq;
|
|
|
|
info.nlmsg_flags = 0;
|
|
|
|
|
|
|
|
err = crypto_report_alg(alg, &info);
|
2015-04-07 06:27:01 -07:00
|
|
|
|
|
|
|
drop_alg:
|
|
|
|
crypto_mod_put(alg);
|
|
|
|
|
2019-10-04 12:29:16 -07:00
|
|
|
if (err) {
|
|
|
|
kfree_skb(skb);
|
2011-09-26 22:23:50 -07:00
|
|
|
return err;
|
2019-10-04 12:29:16 -07:00
|
|
|
}
|
2011-09-26 22:23:50 -07:00
|
|
|
|
2019-07-09 04:11:24 -07:00
|
|
|
return nlmsg_unicast(net->crypto_nlsk, skb, NETLINK_CB(in_skb).portid);
|
2011-09-26 22:23:50 -07:00
|
|
|
}
|
|
|
|
|
|
|
|
static int crypto_dump_report(struct sk_buff *skb, struct netlink_callback *cb)
|
|
|
|
{
|
2018-12-06 16:55:41 -07:00
|
|
|
const size_t start_pos = cb->args[0];
|
|
|
|
size_t pos = 0;
|
2011-09-26 22:23:50 -07:00
|
|
|
struct crypto_dump_info info;
|
2018-12-06 16:55:41 -07:00
|
|
|
struct crypto_alg *alg;
|
|
|
|
int res;
|
2011-09-26 22:23:50 -07:00
|
|
|
|
|
|
|
info.in_skb = cb->skb;
|
|
|
|
info.out_skb = skb;
|
|
|
|
info.nlmsg_seq = cb->nlh->nlmsg_seq;
|
|
|
|
info.nlmsg_flags = NLM_F_MULTI;
|
|
|
|
|
2018-12-06 16:55:41 -07:00
|
|
|
down_read(&crypto_alg_sem);
|
2011-09-26 22:23:50 -07:00
|
|
|
list_for_each_entry(alg, &crypto_alg_list, cra_list) {
|
2018-12-06 16:55:41 -07:00
|
|
|
if (pos >= start_pos) {
|
|
|
|
res = crypto_report_alg(alg, &info);
|
|
|
|
if (res == -EMSGSIZE)
|
|
|
|
break;
|
|
|
|
if (res)
|
|
|
|
goto out;
|
|
|
|
}
|
|
|
|
pos++;
|
2011-09-26 22:23:50 -07:00
|
|
|
}
|
2018-12-06 16:55:41 -07:00
|
|
|
cb->args[0] = pos;
|
|
|
|
res = skb->len;
|
2011-09-26 22:23:50 -07:00
|
|
|
out:
|
2018-12-06 16:55:41 -07:00
|
|
|
up_read(&crypto_alg_sem);
|
|
|
|
return res;
|
2011-09-26 22:23:50 -07:00
|
|
|
}
|
|
|
|
|
|
|
|
static int crypto_dump_report_done(struct netlink_callback *cb)
|
|
|
|
{
|
|
|
|
return 0;
|
|
|
|
}
|
|
|
|
|
|
|
|
static int crypto_update_alg(struct sk_buff *skb, struct nlmsghdr *nlh,
|
|
|
|
struct nlattr **attrs)
|
|
|
|
{
|
|
|
|
struct crypto_alg *alg;
|
|
|
|
struct crypto_user_alg *p = nlmsg_data(nlh);
|
|
|
|
struct nlattr *priority = attrs[CRYPTOCFGA_PRIORITY_VAL];
|
|
|
|
LIST_HEAD(list);
|
|
|
|
|
2014-06-07 19:44:40 -07:00
|
|
|
if (!netlink_capable(skb, CAP_NET_ADMIN))
|
2014-05-08 06:58:12 -07:00
|
|
|
return -EPERM;
|
|
|
|
|
2013-02-05 10:19:15 -07:00
|
|
|
if (!null_terminated(p->cru_name) || !null_terminated(p->cru_driver_name))
|
|
|
|
return -EINVAL;
|
|
|
|
|
2011-09-26 22:23:50 -07:00
|
|
|
if (priority && !strlen(p->cru_driver_name))
|
|
|
|
return -EINVAL;
|
|
|
|
|
|
|
|
alg = crypto_alg_match(p, 1);
|
|
|
|
if (!alg)
|
|
|
|
return -ENOENT;
|
|
|
|
|
|
|
|
down_write(&crypto_alg_sem);
|
|
|
|
|
|
|
|
crypto_remove_spawns(alg, &list, NULL);
|
|
|
|
|
|
|
|
if (priority)
|
|
|
|
alg->cra_priority = nla_get_u32(priority);
|
|
|
|
|
|
|
|
up_write(&crypto_alg_sem);
|
|
|
|
|
2015-04-07 06:27:01 -07:00
|
|
|
crypto_mod_put(alg);
|
2011-09-26 22:23:50 -07:00
|
|
|
crypto_remove_final(&list);
|
|
|
|
|
|
|
|
return 0;
|
|
|
|
}
|
|
|
|
|
|
|
|
static int crypto_del_alg(struct sk_buff *skb, struct nlmsghdr *nlh,
|
|
|
|
struct nlattr **attrs)
|
|
|
|
{
|
|
|
|
struct crypto_alg *alg;
|
|
|
|
struct crypto_user_alg *p = nlmsg_data(nlh);
|
2015-04-07 06:27:01 -07:00
|
|
|
int err;
|
2011-09-26 22:23:50 -07:00
|
|
|
|
2014-06-07 19:44:40 -07:00
|
|
|
if (!netlink_capable(skb, CAP_NET_ADMIN))
|
2014-05-08 06:58:12 -07:00
|
|
|
return -EPERM;
|
|
|
|
|
2013-02-05 10:19:15 -07:00
|
|
|
if (!null_terminated(p->cru_name) || !null_terminated(p->cru_driver_name))
|
|
|
|
return -EINVAL;
|
|
|
|
|
2011-09-26 22:23:50 -07:00
|
|
|
alg = crypto_alg_match(p, 1);
|
|
|
|
if (!alg)
|
|
|
|
return -ENOENT;
|
|
|
|
|
|
|
|
/* We can not unregister core algorithms such as aes-generic.
|
|
|
|
* We would loose the reference in the crypto_alg_list to this algorithm
|
|
|
|
* if we try to unregister. Unregistering such an algorithm without
|
|
|
|
* removing the module is not possible, so we restrict to crypto
|
|
|
|
* instances that are build from templates. */
|
2015-04-07 06:27:01 -07:00
|
|
|
err = -EINVAL;
|
2011-09-26 22:23:50 -07:00
|
|
|
if (!(alg->cra_flags & CRYPTO_ALG_INSTANCE))
|
2015-04-07 06:27:01 -07:00
|
|
|
goto drop_alg;
|
2011-09-26 22:23:50 -07:00
|
|
|
|
2015-04-07 06:27:01 -07:00
|
|
|
err = -EBUSY;
|
2017-12-29 09:00:46 -07:00
|
|
|
if (refcount_read(&alg->cra_refcnt) > 2)
|
2015-04-07 06:27:01 -07:00
|
|
|
goto drop_alg;
|
2011-09-26 22:23:50 -07:00
|
|
|
|
2019-12-15 16:51:19 -07:00
|
|
|
crypto_unregister_instance((struct crypto_instance *)alg);
|
|
|
|
err = 0;
|
2015-04-07 06:27:01 -07:00
|
|
|
|
|
|
|
drop_alg:
|
|
|
|
crypto_mod_put(alg);
|
|
|
|
return err;
|
2011-09-26 22:23:50 -07:00
|
|
|
}
|
|
|
|
|
|
|
|
static int crypto_add_alg(struct sk_buff *skb, struct nlmsghdr *nlh,
|
|
|
|
struct nlattr **attrs)
|
|
|
|
{
|
2012-01-29 15:39:22 -07:00
|
|
|
int exact = 0;
|
2011-09-26 22:23:50 -07:00
|
|
|
const char *name;
|
|
|
|
struct crypto_alg *alg;
|
|
|
|
struct crypto_user_alg *p = nlmsg_data(nlh);
|
|
|
|
struct nlattr *priority = attrs[CRYPTOCFGA_PRIORITY_VAL];
|
|
|
|
|
2014-06-07 19:44:40 -07:00
|
|
|
if (!netlink_capable(skb, CAP_NET_ADMIN))
|
2014-05-08 06:58:12 -07:00
|
|
|
return -EPERM;
|
|
|
|
|
2013-02-05 10:19:15 -07:00
|
|
|
if (!null_terminated(p->cru_name) || !null_terminated(p->cru_driver_name))
|
|
|
|
return -EINVAL;
|
|
|
|
|
2011-09-26 22:23:50 -07:00
|
|
|
if (strlen(p->cru_driver_name))
|
|
|
|
exact = 1;
|
|
|
|
|
|
|
|
if (priority && !exact)
|
|
|
|
return -EINVAL;
|
|
|
|
|
|
|
|
alg = crypto_alg_match(p, exact);
|
2015-04-07 06:27:01 -07:00
|
|
|
if (alg) {
|
|
|
|
crypto_mod_put(alg);
|
2011-09-26 22:23:50 -07:00
|
|
|
return -EEXIST;
|
2015-04-07 06:27:01 -07:00
|
|
|
}
|
2011-09-26 22:23:50 -07:00
|
|
|
|
|
|
|
if (strlen(p->cru_driver_name))
|
|
|
|
name = p->cru_driver_name;
|
|
|
|
else
|
|
|
|
name = p->cru_name;
|
|
|
|
|
2016-07-11 22:17:49 -07:00
|
|
|
alg = crypto_alg_mod_lookup(name, p->cru_type, p->cru_mask);
|
2011-09-26 22:23:50 -07:00
|
|
|
if (IS_ERR(alg))
|
|
|
|
return PTR_ERR(alg);
|
|
|
|
|
|
|
|
down_write(&crypto_alg_sem);
|
|
|
|
|
|
|
|
if (priority)
|
|
|
|
alg->cra_priority = nla_get_u32(priority);
|
|
|
|
|
|
|
|
up_write(&crypto_alg_sem);
|
|
|
|
|
|
|
|
crypto_mod_put(alg);
|
|
|
|
|
|
|
|
return 0;
|
|
|
|
}
|
|
|
|
|
2015-06-21 04:11:45 -07:00
|
|
|
static int crypto_del_rng(struct sk_buff *skb, struct nlmsghdr *nlh,
|
|
|
|
struct nlattr **attrs)
|
|
|
|
{
|
|
|
|
if (!netlink_capable(skb, CAP_NET_ADMIN))
|
|
|
|
return -EPERM;
|
|
|
|
return crypto_del_default_rng();
|
|
|
|
}
|
|
|
|
|
crypto: remove CONFIG_CRYPTO_STATS
Remove support for the "Crypto usage statistics" feature
(CONFIG_CRYPTO_STATS). This feature does not appear to have ever been
used, and it is harmful because it significantly reduces performance and
is a large maintenance burden.
Covering each of these points in detail:
1. Feature is not being used
Since these generic crypto statistics are only readable using netlink,
it's fairly straightforward to look for programs that use them. I'm
unable to find any evidence that any such programs exist. For example,
Debian Code Search returns no hits except the kernel header and kernel
code itself and translations of the kernel header:
https://codesearch.debian.net/search?q=CRYPTOCFGA_STAT&literal=1&perpkg=1
The patch series that added this feature in 2018
(https://lore.kernel.org/linux-crypto/1537351855-16618-1-git-send-email-clabbe@baylibre.com/)
said "The goal is to have an ifconfig for crypto device." This doesn't
appear to have happened.
It's not clear that there is real demand for crypto statistics. Just
because the kernel provides other types of statistics such as I/O and
networking statistics and some people find those useful does not mean
that crypto statistics are useful too.
Further evidence that programs are not using CONFIG_CRYPTO_STATS is that
it was able to be disabled in RHEL and Fedora as a bug fix
(https://gitlab.com/redhat/centos-stream/src/kernel/centos-stream-9/-/merge_requests/2947).
Even further evidence comes from the fact that there are and have been
bugs in how the stats work, but they were never reported. For example,
before Linux v6.7 hash stats were double-counted in most cases.
There has also never been any documentation for this feature, so it
might be hard to use even if someone wanted to.
2. CONFIG_CRYPTO_STATS significantly reduces performance
Enabling CONFIG_CRYPTO_STATS significantly reduces the performance of
the crypto API, even if no program ever retrieves the statistics. This
primarily affects systems with a large number of CPUs. For example,
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2039576 reported
that Lustre client encryption performance improved from 21.7GB/s to
48.2GB/s by disabling CONFIG_CRYPTO_STATS.
It can be argued that this means that CONFIG_CRYPTO_STATS should be
optimized with per-cpu counters similar to many of the networking
counters. But no one has done this in 5+ years. This is consistent
with the fact that the feature appears to be unused, so there seems to
be little interest in improving it as opposed to just disabling it.
It can be argued that because CONFIG_CRYPTO_STATS is off by default,
performance doesn't matter. But Linux distros tend to error on the side
of enabling options. The option is enabled in Ubuntu and Arch Linux,
and until recently was enabled in RHEL and Fedora (see above). So, even
just having the option available is harmful to users.
3. CONFIG_CRYPTO_STATS is a large maintenance burden
There are over 1000 lines of code associated with CONFIG_CRYPTO_STATS,
spread among 32 files. It significantly complicates much of the
implementation of the crypto API. After the initial submission, many
fixes and refactorings have consumed effort of multiple people to keep
this feature "working". We should be spending this effort elsewhere.
Acked-by: Ard Biesheuvel <ardb@kernel.org>
Acked-by: Corentin Labbe <clabbe@baylibre.com>
Signed-off-by: Eric Biggers <ebiggers@google.com>
Signed-off-by: Herbert Xu <herbert@gondor.apana.org.au>
2024-03-12 20:48:21 -07:00
|
|
|
static int crypto_reportstat(struct sk_buff *in_skb, struct nlmsghdr *in_nlh,
|
|
|
|
struct nlattr **attrs)
|
|
|
|
{
|
|
|
|
/* No longer supported */
|
|
|
|
return -ENOTSUPP;
|
|
|
|
}
|
|
|
|
|
2011-09-26 22:23:50 -07:00
|
|
|
#define MSGSIZE(type) sizeof(struct type)
|
|
|
|
|
|
|
|
static const int crypto_msg_min[CRYPTO_NR_MSGTYPES] = {
|
|
|
|
[CRYPTO_MSG_NEWALG - CRYPTO_MSG_BASE] = MSGSIZE(crypto_user_alg),
|
|
|
|
[CRYPTO_MSG_DELALG - CRYPTO_MSG_BASE] = MSGSIZE(crypto_user_alg),
|
|
|
|
[CRYPTO_MSG_UPDATEALG - CRYPTO_MSG_BASE] = MSGSIZE(crypto_user_alg),
|
2016-06-22 11:29:37 -07:00
|
|
|
[CRYPTO_MSG_GETALG - CRYPTO_MSG_BASE] = MSGSIZE(crypto_user_alg),
|
2015-06-21 04:11:45 -07:00
|
|
|
[CRYPTO_MSG_DELRNG - CRYPTO_MSG_BASE] = 0,
|
2018-09-19 03:10:54 -07:00
|
|
|
[CRYPTO_MSG_GETSTAT - CRYPTO_MSG_BASE] = MSGSIZE(crypto_user_alg),
|
2011-09-26 22:23:50 -07:00
|
|
|
};
|
|
|
|
|
|
|
|
static const struct nla_policy crypto_policy[CRYPTOCFGA_MAX+1] = {
|
|
|
|
[CRYPTOCFGA_PRIORITY_VAL] = { .type = NLA_U32},
|
|
|
|
};
|
|
|
|
|
|
|
|
#undef MSGSIZE
|
|
|
|
|
2013-02-24 06:09:12 -07:00
|
|
|
static const struct crypto_link {
|
2011-09-26 22:23:50 -07:00
|
|
|
int (*doit)(struct sk_buff *, struct nlmsghdr *, struct nlattr **);
|
|
|
|
int (*dump)(struct sk_buff *, struct netlink_callback *);
|
|
|
|
int (*done)(struct netlink_callback *);
|
|
|
|
} crypto_dispatch[CRYPTO_NR_MSGTYPES] = {
|
|
|
|
[CRYPTO_MSG_NEWALG - CRYPTO_MSG_BASE] = { .doit = crypto_add_alg},
|
|
|
|
[CRYPTO_MSG_DELALG - CRYPTO_MSG_BASE] = { .doit = crypto_del_alg},
|
|
|
|
[CRYPTO_MSG_UPDATEALG - CRYPTO_MSG_BASE] = { .doit = crypto_update_alg},
|
|
|
|
[CRYPTO_MSG_GETALG - CRYPTO_MSG_BASE] = { .doit = crypto_report,
|
|
|
|
.dump = crypto_dump_report,
|
|
|
|
.done = crypto_dump_report_done},
|
2015-06-21 04:11:45 -07:00
|
|
|
[CRYPTO_MSG_DELRNG - CRYPTO_MSG_BASE] = { .doit = crypto_del_rng },
|
2018-12-13 01:36:37 -07:00
|
|
|
[CRYPTO_MSG_GETSTAT - CRYPTO_MSG_BASE] = { .doit = crypto_reportstat},
|
2011-09-26 22:23:50 -07:00
|
|
|
};
|
|
|
|
|
2017-04-12 05:34:04 -07:00
|
|
|
static int crypto_user_rcv_msg(struct sk_buff *skb, struct nlmsghdr *nlh,
|
|
|
|
struct netlink_ext_ack *extack)
|
2011-09-26 22:23:50 -07:00
|
|
|
{
|
2019-07-09 04:11:24 -07:00
|
|
|
struct net *net = sock_net(skb->sk);
|
2011-09-26 22:23:50 -07:00
|
|
|
struct nlattr *attrs[CRYPTOCFGA_MAX+1];
|
2013-02-24 06:09:12 -07:00
|
|
|
const struct crypto_link *link;
|
2011-09-26 22:23:50 -07:00
|
|
|
int type, err;
|
|
|
|
|
|
|
|
type = nlh->nlmsg_type;
|
|
|
|
if (type > CRYPTO_MSG_MAX)
|
|
|
|
return -EINVAL;
|
|
|
|
|
|
|
|
type -= CRYPTO_MSG_BASE;
|
|
|
|
link = &crypto_dispatch[type];
|
|
|
|
|
|
|
|
if ((type == (CRYPTO_MSG_GETALG - CRYPTO_MSG_BASE) &&
|
|
|
|
(nlh->nlmsg_flags & NLM_F_DUMP))) {
|
2012-03-29 00:04:46 -07:00
|
|
|
struct crypto_alg *alg;
|
2018-12-06 16:55:41 -07:00
|
|
|
unsigned long dump_alloc = 0;
|
2012-03-29 00:04:46 -07:00
|
|
|
|
2011-09-26 22:23:50 -07:00
|
|
|
if (link->dump == NULL)
|
|
|
|
return -EINVAL;
|
2012-03-29 00:04:46 -07:00
|
|
|
|
2016-02-01 06:27:30 -07:00
|
|
|
down_read(&crypto_alg_sem);
|
2012-03-29 00:04:46 -07:00
|
|
|
list_for_each_entry(alg, &crypto_alg_list, cra_list)
|
|
|
|
dump_alloc += CRYPTO_REPORT_MAXSIZE;
|
2018-12-06 16:55:41 -07:00
|
|
|
up_read(&crypto_alg_sem);
|
2012-03-29 00:04:46 -07:00
|
|
|
|
2012-02-24 07:30:15 -07:00
|
|
|
{
|
|
|
|
struct netlink_dump_control c = {
|
|
|
|
.dump = link->dump,
|
|
|
|
.done = link->done,
|
2018-12-06 16:55:41 -07:00
|
|
|
.min_dump_alloc = min(dump_alloc, 65535UL),
|
2012-02-24 07:30:15 -07:00
|
|
|
};
|
2019-07-09 04:11:24 -07:00
|
|
|
err = netlink_dump_start(net->crypto_nlsk, skb, nlh, &c);
|
2012-02-24 07:30:15 -07:00
|
|
|
}
|
2016-02-01 06:27:30 -07:00
|
|
|
|
|
|
|
return err;
|
2011-09-26 22:23:50 -07:00
|
|
|
}
|
|
|
|
|
netlink: make validation more configurable for future strictness
We currently have two levels of strict validation:
1) liberal (default)
- undefined (type >= max) & NLA_UNSPEC attributes accepted
- attribute length >= expected accepted
- garbage at end of message accepted
2) strict (opt-in)
- NLA_UNSPEC attributes accepted
- attribute length >= expected accepted
Split out parsing strictness into four different options:
* TRAILING - check that there's no trailing data after parsing
attributes (in message or nested)
* MAXTYPE - reject attrs > max known type
* UNSPEC - reject attributes with NLA_UNSPEC policy entries
* STRICT_ATTRS - strictly validate attribute size
The default for future things should be *everything*.
The current *_strict() is a combination of TRAILING and MAXTYPE,
and is renamed to _deprecated_strict().
The current regular parsing has none of this, and is renamed to
*_parse_deprecated().
Additionally it allows us to selectively set one of the new flags
even on old policies. Notably, the UNSPEC flag could be useful in
this case, since it can be arranged (by filling in the policy) to
not be an incompatible userspace ABI change, but would then going
forward prevent forgetting attribute entries. Similar can apply
to the POLICY flag.
We end up with the following renames:
* nla_parse -> nla_parse_deprecated
* nla_parse_strict -> nla_parse_deprecated_strict
* nlmsg_parse -> nlmsg_parse_deprecated
* nlmsg_parse_strict -> nlmsg_parse_deprecated_strict
* nla_parse_nested -> nla_parse_nested_deprecated
* nla_validate_nested -> nla_validate_nested_deprecated
Using spatch, of course:
@@
expression TB, MAX, HEAD, LEN, POL, EXT;
@@
-nla_parse(TB, MAX, HEAD, LEN, POL, EXT)
+nla_parse_deprecated(TB, MAX, HEAD, LEN, POL, EXT)
@@
expression NLH, HDRLEN, TB, MAX, POL, EXT;
@@
-nlmsg_parse(NLH, HDRLEN, TB, MAX, POL, EXT)
+nlmsg_parse_deprecated(NLH, HDRLEN, TB, MAX, POL, EXT)
@@
expression NLH, HDRLEN, TB, MAX, POL, EXT;
@@
-nlmsg_parse_strict(NLH, HDRLEN, TB, MAX, POL, EXT)
+nlmsg_parse_deprecated_strict(NLH, HDRLEN, TB, MAX, POL, EXT)
@@
expression TB, MAX, NLA, POL, EXT;
@@
-nla_parse_nested(TB, MAX, NLA, POL, EXT)
+nla_parse_nested_deprecated(TB, MAX, NLA, POL, EXT)
@@
expression START, MAX, POL, EXT;
@@
-nla_validate_nested(START, MAX, POL, EXT)
+nla_validate_nested_deprecated(START, MAX, POL, EXT)
@@
expression NLH, HDRLEN, MAX, POL, EXT;
@@
-nlmsg_validate(NLH, HDRLEN, MAX, POL, EXT)
+nlmsg_validate_deprecated(NLH, HDRLEN, MAX, POL, EXT)
For this patch, don't actually add the strict, non-renamed versions
yet so that it breaks compile if I get it wrong.
Also, while at it, make nla_validate and nla_parse go down to a
common __nla_validate_parse() function to avoid code duplication.
Ultimately, this allows us to have very strict validation for every
new caller of nla_parse()/nlmsg_parse() etc as re-introduced in the
next patch, while existing things will continue to work as is.
In effect then, this adds fully strict validation for any new command.
Signed-off-by: Johannes Berg <johannes.berg@intel.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
2019-04-26 05:07:28 -07:00
|
|
|
err = nlmsg_parse_deprecated(nlh, crypto_msg_min[type], attrs,
|
|
|
|
CRYPTOCFGA_MAX, crypto_policy, extack);
|
2016-06-23 03:06:02 -07:00
|
|
|
if (err < 0)
|
|
|
|
return err;
|
2011-09-26 22:23:50 -07:00
|
|
|
|
|
|
|
if (link->doit == NULL)
|
|
|
|
return -EINVAL;
|
|
|
|
|
|
|
|
return link->doit(skb, nlh, attrs);
|
|
|
|
}
|
|
|
|
|
|
|
|
static void crypto_netlink_rcv(struct sk_buff *skb)
|
|
|
|
{
|
|
|
|
mutex_lock(&crypto_cfg_mutex);
|
|
|
|
netlink_rcv_skb(skb, &crypto_user_rcv_msg);
|
|
|
|
mutex_unlock(&crypto_cfg_mutex);
|
|
|
|
}
|
|
|
|
|
2019-07-09 04:11:24 -07:00
|
|
|
static int __net_init crypto_netlink_init(struct net *net)
|
2011-09-26 22:23:50 -07:00
|
|
|
{
|
2012-06-28 23:15:21 -07:00
|
|
|
struct netlink_kernel_cfg cfg = {
|
|
|
|
.input = crypto_netlink_rcv,
|
|
|
|
};
|
|
|
|
|
2019-07-09 04:11:24 -07:00
|
|
|
net->crypto_nlsk = netlink_kernel_create(net, NETLINK_CRYPTO, &cfg);
|
|
|
|
return net->crypto_nlsk == NULL ? -ENOMEM : 0;
|
|
|
|
}
|
2011-09-26 22:23:50 -07:00
|
|
|
|
2019-07-09 04:11:24 -07:00
|
|
|
static void __net_exit crypto_netlink_exit(struct net *net)
|
|
|
|
{
|
|
|
|
netlink_kernel_release(net->crypto_nlsk);
|
|
|
|
net->crypto_nlsk = NULL;
|
|
|
|
}
|
|
|
|
|
|
|
|
static struct pernet_operations crypto_netlink_net_ops = {
|
|
|
|
.init = crypto_netlink_init,
|
|
|
|
.exit = crypto_netlink_exit,
|
|
|
|
};
|
|
|
|
|
|
|
|
static int __init crypto_user_init(void)
|
|
|
|
{
|
|
|
|
return register_pernet_subsys(&crypto_netlink_net_ops);
|
2011-09-26 22:23:50 -07:00
|
|
|
}
|
|
|
|
|
|
|
|
static void __exit crypto_user_exit(void)
|
|
|
|
{
|
2019-07-09 04:11:24 -07:00
|
|
|
unregister_pernet_subsys(&crypto_netlink_net_ops);
|
2011-09-26 22:23:50 -07:00
|
|
|
}
|
|
|
|
|
|
|
|
module_init(crypto_user_init);
|
|
|
|
module_exit(crypto_user_exit);
|
|
|
|
MODULE_LICENSE("GPL");
|
|
|
|
MODULE_AUTHOR("Steffen Klassert <steffen.klassert@secunet.com>");
|
|
|
|
MODULE_DESCRIPTION("Crypto userspace configuration API");
|
2014-11-24 09:12:45 -07:00
|
|
|
MODULE_ALIAS("net-pf-16-proto-21");
|