Sreekanth, > Broadcom adapters participate in a Secure Boot process, where every > piece of FW is digitally signed by Broadcom and is checked for a valid > signature. If any piece of our adapter FW fails this signature check, > it is possible the FW has been tampered with and the adapter should > not be used. Our driver should not make any additional access to the > “invalid/tampered” adapter because the FW is not valid (could be > malicious FW). This type of detection is added into latest Aero and > Sea family adapters h/w. While I appreciate the intent, I would still like there to be an option to permit using the adapter. I am concerned about users being unable to boot their system due to this if, for whatever reason, these validation checks fail. Maybe there is limited risk of that happening since this is restricted to Aero and Sea adapters. But I am still concerned about enforcing policy decisions like this in the kernel. -- Martin K. Petersen Oracle Linux Engineering
