From c79391c696da0151c6ec8cb8a31edfa8bbe68f24 Mon Sep 17 00:00:00 2001

From: Giovanni Cabiddu <giovanni.cabiddu@intel.com>

Date: Wed, 17 Nov 2021 14:30:34 +0000

Subject: [PATCH] crypto: qat - do not handle PFVF sources for qat_4xxx

Git-commit: c79391c696da0151c6ec8cb8a31edfa8bbe68f24

Patch-mainline: v5.17-rc1

References: jsc#PED-1073

The QAT driver does not have support for PFVF interrupts for GEN4

devices, therefore report the vf2pf sources as 0.

This prevents a NULL pointer dereference in the function

adf_msix_isr_ae() if the device triggers a spurious interrupt.

Fixes: 993161d36ab5 ("crypto: qat - fix handling of VF to PF interrupts")

Reported-by: Adam Guerin <adam.guerin@intel.com>

Signed-off-by: Giovanni Cabiddu <giovanni.cabiddu@intel.com>

Signed-off-by: Herbert Xu <herbert@gondor.apana.org.au>

Signed-off-by: Torsten Duwe <duwe@suse.de>

---

 drivers/crypto/qat/qat_4xxx/adf_4xxx_hw_data.c | 7 +++++++

 1 file changed, 7 insertions(+)

diff --git a/drivers/crypto/qat/qat_4xxx/adf_4xxx_hw_data.c b/drivers/crypto/qat/qat_4xxx/adf_4xxx_hw_data.c

index fa768f10635fd..fd29861526d6b 100644

--- a/drivers/crypto/qat/qat_4xxx/adf_4xxx_hw_data.c

+++ b/drivers/crypto/qat/qat_4xxx/adf_4xxx_hw_data.c

@@ -211,6 +211,12 @@ static u32 uof_get_ae_mask(u32 obj_num)

 	return adf_4xxx_fw_config[obj_num].ae_mask;

 }

+static u32 get_vf2pf_sources(void __iomem *pmisc_addr)

+{

+	/* For the moment do not report vf2pf sources */

+	return 0;

+}

+

 void adf_init_hw_data_4xxx(struct adf_hw_device_data *hw_data)

 {

 	hw_data->dev_class = &adf_4xxx_class;

@@ -254,6 +260,7 @@ void adf_init_hw_data_4xxx(struct adf_hw_device_data *hw_data)

 	hw_data->set_msix_rttable = set_msix_default_rttable;

 	hw_data->set_ssm_wdtimer = adf_gen4_set_ssm_wdtimer;

 	hw_data->enable_pfvf_comms = pfvf_comms_disabled;

+	hw_data->get_vf2pf_sources = get_vf2pf_sources;

 	hw_data->disable_iov = adf_disable_sriov;

 	hw_data->min_iov_compat_ver = ADF_PFVF_COMPAT_THIS_VERSION;

-- 

2.35.3