summaryrefslogtreecommitdiff
path: root/.cocciconfig
diff options
context:
space:
mode:
authorEric Biggers <ebiggers@google.com>2018-12-06 07:53:00 +0300
committerMike Snitzer <snitzer@redhat.com>2018-12-18 17:02:27 +0300
commitaf331ebae7e10699a023fcce4f0671a01419ee3c (patch)
tree53ee7af5183e099e6514b6bb1579df7e3d5a3265 /.cocciconfig
parente8c2566f83527f6bcced86739adc5cd5262e2dd2 (diff)
downloadlinux-af331ebae7e10699a023fcce4f0671a01419ee3c.tar.xz
dm crypt: log the encryption algorithm implementation
Log the encryption algorithm's driver name when a dm-crypt target is created. This will help people determine whether the expected implementation is being used. In some cases we've seen people do benchmarks and reject using encryption for performance reasons, when in fact they used a much slower implementation than was possible on the hardware. It can make an enormous difference; e.g., AES-XTS on ARM can be over 10x faster with the crypto extensions than without. It can also be useful to know if an implementation using an external crypto accelerator is being used instead of a software implementation. Example message: [ 29.307629] device-mapper: crypt: xts(aes) using implementation "xts-aes-ce" We've already found the similar message in fs/crypto/keyinfo.c to be very useful. Signed-off-by: Eric Biggers <ebiggers@google.com> Signed-off-by: Mike Snitzer <snitzer@redhat.com>
Diffstat (limited to '.cocciconfig')
0 files changed, 0 insertions, 0 deletions