[dpdk-test-report] |FAILURE| pw65932[1/2] net/bnxt: fix segmentation fault handling async events on port stop

[dpdk-test-report] |FAILURE| pw65932[1/2] net/bnxt: fix segmentation fault handling async events on port stop

[sys_stv]

[-- Attachment #1: Type: text/plain, Size: 1544 bytes --]

Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/65932

_apply issues_

Submitter: Kalesh A P <kalesh-anakkur.purayil@broadcom.com>
Date: 2020-02-20 04:12:13
Reply_mail: 20200220041214.18053-2-kalesh-anakkur.purayil@broadcom.com
DPDK git baseline:
	Repo:dpdk-next-net-brcm, CommitID: 8f8a67919c98bb3ee71db3c22697fc4808630126
	Repo:dpdk, CommitID: fbd54248bb18040166a3e6d792282bd5ca5ed240

*Repo: dpdk-next-net-brcm
forwarding is not started on Stingray devices, driver will not receive
    the async event from FW when there is a FW reset. While exiting testpmd,
    as part of port stop driver sees this event and this in turn causes a
    race between port stop and error recovery task.
    
    Fixed this by ignoring the fatal/non-fatal async event from FW while
    stopping port.
    
    Fixes: df6cd7c1f73a ("net/bnxt: handle reset notify async event from FW")
    Cc: stable@dpdk.org
    
--
	rte_spinlock_lock(&bp->hwrm_lock); \
	memset(bp->hwrm_cmd_resp_addr, 0, bp->max_resp_len); \
	req.req_type = rte_cpu_to_le_16(HWRM_##type); \
	req.cmpl_ring = rte_cpu_to_le_16(-1); \

error: patch failed: drivers/net/bnxt/bnxt_hwrm.c:184
error: drivers/net/bnxt/bnxt_hwrm.c: patch does not apply
*Repo: dpdk
rte_spinlock_lock(&bp->hwrm_lock); \
	memset(bp->hwrm_cmd_resp_addr, 0, bp->max_resp_len); \
	req.req_type = rte_cpu_to_le_16(HWRM_##type); \
	req.cmpl_ring = rte_cpu_to_le_16(-1); \

error: patch failed: drivers/net/bnxt/bnxt_hwrm.c:184
error: drivers/net/bnxt/bnxt_hwrm.c: patch does not apply

DPDK STV team