Private bug reported:
NVMe Command Lockdown
Dell's BMC will be doing the lockdown out-of-band and that does not
require any OS support. Once a command is locked down, then if the OS
issues a command that is locked down, they will get an error status of
Command Prohibited by Command and Feature Lockdown. So we are just
asking for OS to gracefully handle this. For example, the device should
not be marked as bad or failed for this status code. If there’s any
messaging to the user then it can inform the user that some software in
the OS or the BMC has locked down the command and must be unlocked for
the command to succeed.
** Affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Information type changed from Public to Private
** Description changed:
NVMe Command Lockdown
+
+ Dell's BMC will be doing the lockdown out-of-band and that does not
+ require any OS support. Once a command is locked down, then if the OS
+ issues a command that is locked down, they will get an error status of
+ Command Prohibited by Command and Feature Lockdown. So we are just
+ asking for OS to gracefully handle this. For example, the device should
+ not be marked as bad or failed for this status code. If there’s any
+ messaging to the user then it can inform the user that some software in
+ the OS or the BMC has locked down the command and must be unlocked for
+ the command to succeed.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2051277
Title:
Include NVMe Command Lockdown Support on Ubuntu 24.04
Status in linux package in Ubuntu:
New
Bug description:
NVMe Command Lockdown
Dell's BMC will be doing the lockdown out-of-band and that does not
require any OS support. Once a command is locked down, then if the OS
issues a command that is locked down, they will get an error status of
Command Prohibited by Command and Feature Lockdown. So we are just
asking for OS to gracefully handle this. For example, the device
should not be marked as bad or failed for this status code. If there’s
any messaging to the user then it can inform the user that some
software in the OS or the BMC has locked down the command and must be
unlocked for the command to succeed.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2051277/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
