mirror of https://github.com/wolfSSL/wolfssl.git
linuxkm/lkcapi_glue.c: change WOLFSSL_LINUXKM_LKCAPI_PRIORITY from INT_MAX to 100000 to avoid overflows in kernel calculation of priority on constructed algs.
parent
6eb8dfb769
commit
8a3a5929b8
|
@ -56,8 +56,14 @@
|
||||||
#ifndef WOLFSSL_LINUXKM_LKCAPI_PRIORITY
|
#ifndef WOLFSSL_LINUXKM_LKCAPI_PRIORITY
|
||||||
/* Larger number means higher priority. The highest in-tree priority is
|
/* Larger number means higher priority. The highest in-tree priority is
|
||||||
* 4001, in the Cavium driver.
|
* 4001, in the Cavium driver.
|
||||||
|
*
|
||||||
|
* Note bene, when the kernel dynamically constructs compound algorithms, it
|
||||||
|
* computes their priorities by multiplying the priority of the base
|
||||||
|
* algorithm by up to 10, and/or adding to it the priority of a second base
|
||||||
|
* algorithm, or a constant up to 200, so it's not safe to use a value near
|
||||||
|
* INT_MAX here.
|
||||||
*/
|
*/
|
||||||
#define WOLFSSL_LINUXKM_LKCAPI_PRIORITY INT_MAX
|
#define WOLFSSL_LINUXKM_LKCAPI_PRIORITY 100000
|
||||||
#endif
|
#endif
|
||||||
|
|
||||||
#ifdef CONFIG_CRYPTO_MANAGER_EXTRA_TESTS
|
#ifdef CONFIG_CRYPTO_MANAGER_EXTRA_TESTS
|
||||||
|
|
Loading…
Reference in New Issue