Skip to content

ima: use asynchronous hash API for hash calculation

Dmitry Kasatkin linux-crypto lkml 2 versions – In review

Get series with b4
b4 am [email protected]

Versions newest first · linked by author and title

  1. v3 Latest3 patches 11 repliesIn review
  2. v13 patches 6 repliesSuperseded

Changes in v3 from the cover letter

- kernel parameters replaced with module parameters
- more clear comments and function descriptions
- pr_crit replaced with pr_crit_ratelimited

Patches in v3 No applies recorded yet

#Subject and filesSizeRepliesApplied
1/3ima: use ahash API for file hash calculationDocumentation/kernel-parameters.txt security/integrity/ima/ima_crypto.c+190 -411 replies
2/3ima: introduce multi-page collect buffersDocumentation/kernel-parameters.txt security/integrity/ima/ima_crypto.c+104 -20 replies
3/3ima: provide double buffering for hash calculationsecurity/integrity/ima/ima_crypto.c+51 -160 replies

Reviews trailers per patch

No Reviewed-by, Acked-by or Tested-by trailers for v3 yet.

Read the v3 thread

Cover letter [PATCH v3 0/3] ima: use asynchronous hash API for hash calculation

Depending on the IMA policy, it might require to measure huge amount of files. It may be very important to speedup hash calculation or to reduce (battery) energy required to do it. Currently IMA uses synchronous hash API (shash) which is CPU based. CPU based hash calculation is very CPU intensive and on the battery powered device will be also high energy consuming.

Many platforms provide cryptographic acceleration modules which allow speedup and/or reduce energy consumption, and provide asynchronous way to calculate hashes. Defacto way to implement drivers for such accelerators is using asynchronous hash API (ahash).

The first patch adds use of ahash API to IMA. Performance of using HW acceleration depends very much on amount of data to hash and it depends on particular HW. It is usually inefficient for small data due to HW initialization overhead. In order to make it possible to optimize performance for particular system, the patch provides kernel module parameter 'ima.ahash_minsize=<min_file_size>', which allows to specify optimal file size when start using ahash. By default ahash is disabled until non-zero value is specified.

Second patch introduces multi-page buffers which makes HW acceleration more efficient. It provides 'ima.ahash_bufsize=<bufsize>' module parameter to specify buffer size. Buffer is 4k if parameter is unspecified.

Third patch introduces double-buffering which allows to readahead next portion of data for hashing while calculating the hash.

Changes in v3:
- kernel parameters replaced with module parameters
- more clear comments and function descriptions
- pr_crit replaced with pr_crit_ratelimited

Changes in v2:
- ima_ahash_size and ima_ahash_bufsize were combined as ima_ahash
- ahash pre-allocation moved out from __init code to be able to use ahash crypto modules. Ahash allocated once on the first use.
- hash calculation falls back to sahsh if ahash allocation/calculation fails
- complex initialization separated from variable declaration
- improved comments

- Dmitry

Dmitry Kasatkin (3):
ima: use ahash API for file hash calculation
ima: introduce multi-page collect buffers
ima: provide double buffering for hash calculation

 Documentation/kernel-parameters.txt |  17 ++
 security/integrity/ima/ima_crypto.c | 312 +++++++++++++++++++++++++++++++++++-
 2 files changed, 326 insertions(+), 3 deletions(-)
Signature · 1 line
1.9.1