Public bug reported:
SRU Justification:
[Impact]
There is a gap in the mlxbf-bootctl driver logic, resulting in failure to
report when a secure boot enabled card is using development keys. The program
will instead report lifecycle state as "GA Secured" which is misleading.
[Fix]
Bring in the following upstream commit from linux-next:
"mlxbf-bootctl: correctly identify secure boot with development keys"
[Test Case]
Enable secure boot on a BF3 card that is using development keys
Login as root on BF3
Run the command "mlxbf-bootctl"
Verify that the "lifecycle state" row shows "Secured (development)"
[Regression Potential]
Low risk change, cherry pick of upstream approved commit
** Affects: linux-bluefield (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-bluefield in Ubuntu.
https://bugs.launchpad.net/bugs/2045919
Title:
mlxbf-bootctl: fails to report info about cards using dev keys
Status in linux-bluefield package in Ubuntu:
New
Bug description:
SRU Justification:
[Impact]
There is a gap in the mlxbf-bootctl driver logic, resulting in failure to
report when a secure boot enabled card is using development keys. The program
will instead report lifecycle state as "GA Secured" which is misleading.
[Fix]
Bring in the following upstream commit from linux-next:
"mlxbf-bootctl: correctly identify secure boot with development keys"
[Test Case]
Enable secure boot on a BF3 card that is using development keys
Login as root on BF3
Run the command "mlxbf-bootctl"
Verify that the "lifecycle state" row shows "Secured (development)"
[Regression Potential]
Low risk change, cherry pick of upstream approved commit
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/2045919/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : [email protected]
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
