Commit
f6b139b added return status handling to PciIo->Mem.Write.
However, the second status handling will override EFI_DEVICE_ERROR
returned in this branch:
//
// Check the NVMe cmd execution result
//
if (Status != EFI_TIMEOUT) {
if ((Cq->Sct == 0) && (Cq->Sc == 0)) {
Status = EFI_SUCCESS;
} else {
Status = EFI_DEVICE_ERROR;
^^^^^^^^^^^^^^^^
Since PciIo->Mem.Write will probably return SUCCESS, it causes
NvmExpressPassThru to return SUCCESS even when DEVICE_ERROR occurs.
Callers of NvmExpressPassThru will then continue executing which may
cause further unexpected results, e.g. DiscoverAllNamespaces couldn't
break out the loop.
So we save previous status before calling PciIo->Mem.Write and restore
the previous one if it already contains error.
Contributed-under: TianoCore Contribution Agreement 1.1
Signed-off-by: Heyi Guo <heyi.guo@linaro.org>
Cc: Eric Dong <eric.dong@intel.com>
Cc: Ruiyu Ni <ruiyu.ni@intel.com>
Reviewed-by: Hao Wu <hao.a.wu@intel.com>
Reviewed-by: Star Zeng <star.zeng@intel.com>
{\r
NVME_CONTROLLER_PRIVATE_DATA *Private;\r
EFI_STATUS Status;\r
+ EFI_STATUS PreviousStatus;\r
EFI_PCI_IO_PROTOCOL *PciIo;\r
NVME_SQ *Sq;\r
NVME_CQ *Cq;\r
}\r
\r
Data = ReadUnaligned32 ((UINT32*)&Private->CqHdbl[QueueId]);\r
+ PreviousStatus = Status;\r
Status = PciIo->Mem.Write (\r
PciIo,\r
EfiPciIoWidthUint32,\r
1,\r
&Data\r
);\r
+ // The return status of PciIo->Mem.Write should not override\r
+ // previous status if previous status contains error.\r
+ Status = EFI_ERROR (PreviousStatus) ? PreviousStatus : Status;\r
\r
//\r
// For now, the code does not support the non-blocking feature for admin queue.\r