sfc: Explain why efx_mcdi_exit_assertion() ignores result of efx_mcdi_rpc()
Fix CID 113952 in Coverity report on Linux. This is the one instance where we don't, and shouldn't, check the return code from efx_mcdi_rpc(). It wasn't immediately obvious to me why we didn't, so I think an explanation is in order. Signed-off-by: Ben Hutchings <bhutchings@solarflare.com>
This commit is contained in:
parent
e3ed2bdfc4
commit
0f1e54ae52
|
@ -1001,11 +1001,16 @@ static void efx_mcdi_exit_assertion(struct efx_nic *efx)
|
||||||
{
|
{
|
||||||
u8 inbuf[MC_CMD_REBOOT_IN_LEN];
|
u8 inbuf[MC_CMD_REBOOT_IN_LEN];
|
||||||
|
|
||||||
/* Atomically reboot the mcfw out of the assertion handler */
|
/* If the MC is running debug firmware, it might now be
|
||||||
|
* waiting for a debugger to attach, but we just want it to
|
||||||
|
* reboot. We set a flag that makes the command a no-op if it
|
||||||
|
* has already done so. We don't know what return code to
|
||||||
|
* expect (0 or -EIO), so ignore it.
|
||||||
|
*/
|
||||||
BUILD_BUG_ON(MC_CMD_REBOOT_OUT_LEN != 0);
|
BUILD_BUG_ON(MC_CMD_REBOOT_OUT_LEN != 0);
|
||||||
MCDI_SET_DWORD(inbuf, REBOOT_IN_FLAGS,
|
MCDI_SET_DWORD(inbuf, REBOOT_IN_FLAGS,
|
||||||
MC_CMD_REBOOT_FLAGS_AFTER_ASSERTION);
|
MC_CMD_REBOOT_FLAGS_AFTER_ASSERTION);
|
||||||
efx_mcdi_rpc(efx, MC_CMD_REBOOT, inbuf, MC_CMD_REBOOT_IN_LEN,
|
(void) efx_mcdi_rpc(efx, MC_CMD_REBOOT, inbuf, MC_CMD_REBOOT_IN_LEN,
|
||||||
NULL, 0, NULL);
|
NULL, 0, NULL);
|
||||||
}
|
}
|
||||||
|
|
||||||
|
|
Loading…
Reference in New Issue