PKA reboot flow kernel traces

Bug #1916289 reported by Mahantesh Salimath on 2021-02-19
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux-bluefield (Ubuntu)

Bug Description

On some Bluefield platforms, the reboot flow leaves PKA traces in the kernel.
This is due to PKA being corrupt on boot-up due to multiple applications using PKA at the same time.
Handling multiple applications requires a new feature in the PKA driver.

SRU Justification:

* Kernel traces are seen at startup on Bluefield platforms (by Mellanox/Nvidia) due to applications using public key accelerator (PKA) hardware simultaneously.

* Allow synchronized usage of PKA hardware resources "pka: Handle ring open scenario when rings are busy"

[Test Case]
* Trigger multiple processes/applications to use PKA HW simultaneously, this can be done via OpenSSL. Run the OpenSSL speed test with multiple processes using 'pka' engine. Ex: openssl speed -multi 2 -engine pka rsa512
* Note: On Bluefield platforms the OpenSSL dynamic engine (-engine pka, in the above example) is loaded by default.

[Regression Potential]
* The regression can be considered as low, since the rings are shared in a synchronized manner there is no corruption due to different applications running concurrently.
* As there are limited resources (PKA rings) available, if exhausted, can cause applications fail to execute (due to resource unavailability). This is an expected behaviour.

* Note: Unit of PKA HW available for application usage is called a ring.

description: updated
Changed in linux-bluefield (Ubuntu Focal):
status: New → In Progress
importance: Undecided → Medium
Changed in linux-bluefield (Ubuntu):
status: New → Invalid
Stefan Bader (smb) on 2021-02-26
Changed in linux-bluefield (Ubuntu Focal):
status: In Progress → Fix Committed
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Duplicates of this bug

Other bug subscribers