> -----Original Message-----
> From: Zhang, Qi Z <[email protected]>
> Sent: Monday, May 9, 2022 10:05 AM
> To: Zhou, YidingX <[email protected]>; [email protected]; Wu, Jingjing
> <[email protected]>; Xing, Beilei <[email protected]>
> Cc: Yang, Qiming <[email protected]>; [email protected]; Yeleswarapu,
> Ramamani <[email protected]>
> Subject: RE: [PATCH v2] net/iavf: fix mismatch between rx_pkt_burst and RX
> descriptor
>
>
>
> > -----Original Message-----
> > From: Zhou, YidingX <[email protected]>
> > Sent: Sunday, May 8, 2022 3:53 AM
> > To: [email protected]; Wu, Jingjing <[email protected]>; Xing, Beilei
> > <[email protected]>
> > Cc: Yang, Qiming <[email protected]>; Zhang, Qi Z
> > <[email protected]>; [email protected]; Yeleswarapu, Ramamani
> > <[email protected]>
> > Subject: [PATCH v2] net/iavf: fix mismatch between rx_pkt_burst and RX
> > descriptor
Refined the title to " fix wrong data path selection which cause segment fault"
In dpdk-next-net-intel to make it clear what it is going to fix.
> >
> > Some kernel drivers return the capability
> > VIRTCHNL_VF_OFFLOAD_RX_FLEX_DESC when IAVF_RXDID_COMMS_OVS_1
> is not
> > supported. This causes PMD to use rx_pkt_burst that handles the Flex
> > Receive Descriptor format, but actually configures the RXDID into
> > IAVF_RXDID_LEGACY_1, then the fields of rte_mbuf Will be filled with
> > wrong values in rx_pkt_burst, which will eventually lead to coredump.
> >
> > This patch fixes mismatch between rx_pkt_burst and rx descriptor.
> >
> > Fixes: 12b435bf8f2f ("net/iavf: support flex desc metadata
> > extraction")
> > Cc: [email protected]
> >
> > Signed-off-by: Yiding Zhou <[email protected]>
>
> Acked-by: Qi Zhang <[email protected]>
>
> Applied to dpdk-next-net-intel.
>
> Thanks
> Qi
