On Mon, Dec 28, 2020 at 5:48 PM Nithin Dabilpuram wrote:
>
> On Mon, Dec 21, 2020 at 07:33:08PM +0530, sk...@marvell.com wrote:
> > From: Sunil Kumar Kori
> >
> > On Tx, lastseg->next is not being reset to null for multi segmented packet
> > and same mbuf can be used on Rx which has a stale mbuf
On Mon, Dec 21, 2020 at 07:33:08PM +0530, sk...@marvell.com wrote:
> From: Sunil Kumar Kori
>
> On Tx, lastseg->next is not being reset to null for multi segmented packet
> and same mbuf can be used on Rx which has a stale mbuf entry into
> mbuf->next.
>
> On Rx, application receives mbuf with m
From: Sunil Kumar Kori
On Tx, lastseg->next is not being reset to null for multi segmented packet
and same mbuf can be used on Rx which has a stale mbuf entry into
mbuf->next.
On Rx, application receives mbuf with mbuf->next uninitialized though
mbuf->nb_segs is correct. Application iterates ove
3 matches
Mail list logo
