> -----Original Message----- > From: Zhang, Qi Z > Sent: Tuesday, August 22, 2023 3:59 PM > To: 'David Marchand' <[email protected]> > Cc: [email protected]; [email protected]; [email protected]; > [email protected]; Wu, Jingjing <[email protected]>; Xing, Beilei > <[email protected]>; Doherty, Declan <[email protected]>; Sinha, > Abhijit <[email protected]>; Nicolau, Radu <[email protected]> > Subject: RE: [PATCH] net/iavf: fix checksum offloading > > > > > -----Original Message----- > > From: David Marchand <[email protected]> > > Sent: Tuesday, August 22, 2023 3:40 PM > > To: Zhang, Qi Z <[email protected]> > > Cc: [email protected]; [email protected]; [email protected]; > > [email protected]; Wu, Jingjing <[email protected]>; Xing, Beilei > > <[email protected]>; Doherty, Declan <[email protected]>; > > Sinha, Abhijit <[email protected]>; Nicolau, Radu > > <[email protected]> > > Subject: Re: [PATCH] net/iavf: fix checksum offloading > > > > On Tue, Aug 22, 2023 at 9:33 AM Zhang, Qi Z <[email protected]> wrote: > > > > If the driver reads l2_len or l3_len, this is an undefined behavior: > > > > for example, OVS might have been using l2_len or l3_len for its > > > > internal uses (though I agree it would be risky for an application to > > > > do so). > > > > > > > > We probably need to fix access to l2_len a few lines before my patch. > > > > > > > > if (m->ol_flags & RTE_MBUF_F_TX_TUNNEL_MASK && > > > > !(m->ol_flags & RTE_MBUF_F_TX_SEC_OFFLOAD)) > > > > offset |= (m->outer_l2_len >> 1) > > > > << IAVF_TX_DESC_LENGTH_MACLEN_SHIFT; > > > > else > > > > offset |= (m->l2_len >> 1) > > > > << IAVF_TX_DESC_LENGTH_MACLEN_SHIFT; > > > >
After second thought, I think your patch looks good, will you submit a new version to cover above fix?
