> -----Original Message-----
> From: Stephen Hemminger <step...@networkplumber.org>
> Sent: Wednesday, December 6, 2023 2:34 AM
> To: Joyce Kong <joyce.k...@arm.com>
> Cc: Jakub Grajciar <jgraj...@cisco.com>; Morten Brørup
> <m...@smartsharesystems.com>; Ruifeng Wang <ruifeng.w...@arm.com>;
> dev@dpdk.org; nd <n...@arm.com>; sta...@dpdk.org; Liangxing Wang
> <liangxing.w...@arm.com>
> Subject: Re: [PATCH v1] net/memif: fix segfault with Tx burst larger than 255
>
> On Tue, 5 Dec 2023 04:05:24 +0000
> Joyce Kong <joyce.k...@arm.com> wrote:
>
> > There will be a segfault when tx burst size is larger than 256. This
> > is because eth_memif_tx uses an index i which is uint8_t to count
> > transmitted nb_pkts. Extend i to uint16_t, the same size as nb_pkts.
> >
> > Fixes: b5613c8f9d0a ("net/memif: add a Tx fast path")
> > Cc: sta...@dpdk.org
> >
> > Reported-by: Liangxing Wang <liangxing.w...@arm.com>
> > Signed-off-by: Joyce Kong <joyce.k...@arm.com>
> > Reviewed-by: Ruifeng Wang <ruifeng.w...@arm.com>
> > ---
>
> I wonder if other drivers have same bug?
I don't think this is a common bug.
This is a special case as the bug is introduced for whether choosing the memif
Tx fast path.
>
> Reviewed-by: Stephen Hemminger <step...@networkplumber.org>
