Re: [PATCH] igc: fix invalid length and corrupted multi-segment mbufs

2024-11-01 Thread Bruce Richardson
On Fri, Nov 01, 2024 at 02:42:20PM +0100, Martin Weiser wrote: > Hi Bruce, > > thank you very much for your feedback. > Please see my answers inline below. > > I will send a v2 of the patch. > > Best regards, > Martin > > > Am 29.10.24 um 18:42 schrieb Bruce Richardson: > > On Mon, Oct 28, 202

Re: [PATCH] igc: fix invalid length and corrupted multi-segment mbufs

2024-11-01 Thread Martin Weiser
Hi Bruce, thank you very much for your feedback. Please see my answers inline below. I will send a v2 of the patch. Best regards, Martin Am 29.10.24 um 18:42 schrieb Bruce Richardson: > On Mon, Oct 28, 2024 at 03:17:07PM +0100, Martin Weiser wrote: >> >> The issue only appeared with hardware-t

Re: [PATCH] igc: fix invalid length and corrupted multi-segment mbufs

2024-10-29 Thread Bruce Richardson
On Mon, Oct 28, 2024 at 03:17:07PM +0100, Martin Weiser wrote: > > The issue only appeared with hardware-timestamping enabled > (RTE_ETH_RX_OFFLOAD_TIMESTAMP). > > The length of the prepended hardware timestamp was not subtracted from > the data length so that received packets were 16 bytes longe

[PATCH] igc: fix invalid length and corrupted multi-segment mbufs

2024-10-28 Thread Martin Weiser
The issue only appeared with hardware-timestamping enabled (RTE_ETH_RX_OFFLOAD_TIMESTAMP). The length of the prepended hardware timestamp was not subtracted from the data length so that received packets were 16 bytes longer than expected. In scatter-gather mode only the first mbuf has a timesta

[PATCH] igc: fix invalid length and corrupted multi-segment mbufs

2024-10-28 Thread Martin Weiser
The issue only appeared with hardware-timestamping enabled (RTE_ETH_RX_OFFLOAD_TIMESTAMP). The length of the prepended hardware timestamp was not subtracted from the data length so that received packets were 16 bytes longer than expected. In scatter-gather mode only the first mbuf has a timestam