ionic: check cmd_regs before copying in or out
authorShannon Nelson <shannon.nelson@amd.com>
Fri, 23 Feb 2024 22:27:41 +0000 (14:27 -0800)
committerPaolo Abeni <pabeni@redhat.com>
Tue, 27 Feb 2024 12:03:32 +0000 (13:03 +0100)
commit7662fad348ac54120e9e6443cb0bbe4f3b582219
treeb1a1ad1ce2f10926527cdd90a4e1471123d2b601
parenta36b0787f074d7441f66c172745653570e09c320
ionic: check cmd_regs before copying in or out

Since we now have potential cases of NULL cmd_regs and info_regs
during a reset recovery, and left NULL if a reset recovery has
failed, we need to check that they exist before we use them.
Most of the cases were covered in the original patch where we
verify before doing the ioreadb() for health or cmd status.
However, we need to protect a few uses of io mem that could
be hit in error recovery or asynchronous threads calls as well
(e.g. ethtool or devlink handlers).

Fixes: 219e183272b4 ("ionic: no fw read when PCI reset failed")
Reviewed-by: Brett Creeley <brett.creeley@amd.com>
Signed-off-by: Shannon Nelson <shannon.nelson@amd.com>
Signed-off-by: Paolo Abeni <pabeni@redhat.com>
drivers/net/ethernet/pensando/ionic/ionic_dev.c
drivers/net/ethernet/pensando/ionic/ionic_ethtool.c
drivers/net/ethernet/pensando/ionic/ionic_fw.c
drivers/net/ethernet/pensando/ionic/ionic_main.c