net: macb: fix zero UDPv4 checksum on transmit
Subsystems (3)
cover net: macb: fix zero UDPv4 checksum on transmit
When a UDPv4 checksum computes to zero, RFC 768 wants 0xffff on the wire, but the GEM sends the raw 0x0000, which receivers read as "no checksum". Raspberry Pi confirmed in a simulation of the Cadence IP that the engine skips the substitution for UDPv4. UDPv6 and TCP are fine, and the IP changelog suggests all GEM revisions could be affected. Reported and analyzed on the Raspberry Pi 5:
https://github.com/raspberrypi/linux/issues/7550
Patch 2 does UDPv4 checksums in software and lets the existing pad and FCS path keep the hardware off the frame, UDPv6 and TCP keep the offload. That path miscounts tx_bytes by the software FCS, so patch 1 fixes the accounting first.
Tested on CM5. To reproduce, send bulk UDP to another host and capture zero checksums on the receiving side:
iperf3 -c <host> -u -b 200M -t 30
tcpdump -ni <iface> 'src host <dut> and udp[6:2] == 0'
Without the fix a packet shows up every few seconds:
12:46:20.002739 IP <dut>.36309 > <host>.5201: UDP, length 1448 12:46:23.773968 IP <dut>.36309 > <host>.5201: UDP, length 1448 12:46:40.227460 IP <dut>.36309 > <host>.5201: UDP, length 1448
With the fix the capture showed none.
Some numbers (udpgso_bench):
- 18-byte UDP throughput dropped by ~ 8%
- 256-byte UDP throughput dropped by ~ 10%
- MTU-sized UDP and UDP GSO were unchanged at the 116 MiB/s link limit
Unfortunately I don't see a cheaper fix, the zero only shows up after computing the checksum, the MAC inserts it in flight, and AFAIU there is no register or descriptor bit for the substitution.
I'd appreciate testing on other silicon.
Nicolai Buchwitz (2):
net: macb: exclude software FCS from TX byte statistics
net: macb: fix zero UDPv4 checksum on transmit
drivers/net/ethernet/cadence/macb.h | 3 +++ drivers/net/ethernet/cadence/macb_main.c | 28 +++++++++++++++++++++------- 2 files changed, 24 insertions(+), 7 deletions(-)
Signature · 1 line
2.53.0
PATCH 1/2 net: macb: exclude software FCS from TX byte statistics
Frames going through macb_pad_and_fcs() get padded and four FCS bytes appended, and TX completion then accounts the grown skb->len. tx_bytes is supposed to exclude the FCS, and frames padded by the hardware are counted without the padding anyway, so these frames show up too large in the statistics.
Remember the length the stack handed over and use that for the byte counters. BQL stays on the padded skb->len that netdev_tx_sent_queue() saw.
--- drivers/net/ethernet/cadence/macb.h | 3 +++ drivers/net/ethernet/cadence/macb_main.c | 17 ++++++++++------- 2 files changed, 13 insertions(+), 7 deletions(-)
drivers/net/ethernet/cadence/macb.h +3 -0
@@ -968,6 +968,8 @@ struct macb_dma_desc_ptp {* of the frame * @mapping: DMA address of the skb's fragment buffer * @size: size of the DMA mapped buffer +* @skb_len: skb->len as handed over by the stack, before padding and +* software FCS, only set for the last buffer of the frame * @mapped_as_page: true when buffer was mapped with skb_frag_dma_map(), * false when buffer was mapped with dma_map_single() */
@@ -975,6 +977,7 @@ struct macb_tx_skb {struct sk_buff *skb;dma_addr_t mapping;size_t size; +unsigned int skb_len;bool mapped_as_page; };
drivers/net/ethernet/cadence/macb_main.c +10 -7
@@ -1322,8 +1322,8 @@ static void macb_tx_error_task(struct work_struct *work) bp->netdev->stats.tx_packets++; queue->stats.tx_packets++; packets++; - bp->netdev->stats.tx_bytes += skb->len; - queue->stats.tx_bytes += skb->len; + bp->netdev->stats.tx_bytes += tx_skb->skb_len; + queue->stats.tx_bytes += tx_skb->skb_len; bytes += skb->len; } }else {
@@ -1450,8 +1450,8 @@ static int macb_tx_complete(struct macb_queue *queue, int budget) skb->data); bp->netdev->stats.tx_packets++; queue->stats.tx_packets++; - bp->netdev->stats.tx_bytes += skb->len; - queue->stats.tx_bytes += skb->len; + bp->netdev->stats.tx_bytes += tx_skb->skb_len; + queue->stats.tx_bytes += tx_skb->skb_len; packets++; bytes += skb->len; }
@@ -2199,7 +2199,8 @@ static void macb_poll_controller(struct net_device *netdev)static unsigned int macb_tx_map (struct macb *bp,struct macb_queue *queue,struct sk_buff *skb, -unsigned int hdrlen) +unsigned int hdrlen, +unsigned int skb_len) {unsigned int f, nr_frags =skb_shinfo (skb)->nr_frags;unsigned int len, i, tx_head = queue->tx_head;
@@ -2284,6 +2285,7 @@ static unsigned int macb_tx_map(struct macb *bp,/* This is the last buffer of the frame: save socket buffer */ tx_skb->skb = skb; + tx_skb->skb_len = skb_len;/* Update TX ring: update buffer descriptors in reverse order * to avoid race condition
@@ -2476,7 +2478,7 @@ static netdev_tx_t macb_start_xmit(struct sk_buff *skb,unsigned int desc_cnt, nr_frags, frag_size, f;struct macb_queue *queue = &bp->queues[q];netdev_tx_t ret =NETDEV_TX_OK ; -unsigned int hdrlen; +unsigned int hdrlen, skb_len;unsigned long flags;bool is_lso;
@@ -2485,6 +2487,7 @@ static netdev_tx_t macb_start_xmit(struct sk_buff *skb,return ret; } + skb_len = skb->len;if (macb_pad_and_fcs (&skb, netdev)) {dev_kfree_skb_any (skb);return ret;
@@ -2548,7 +2551,7 @@ static netdev_tx_t macb_start_xmit(struct sk_buff *skb, }/* Map socket buffer for DMA transfer */ -if (macb_tx_map (bp, queue, skb, hdrlen)) { +if (macb_tx_map (bp, queue, skb, hdrlen, skb_len)) {dev_kfree_skb_any (skb); goto unlock; }
Signature · 1 line
2.53.0
Re: [PATCH net 1/2] net: macb: exclude software FCS from TX byte statistics
Replying to netdev's sashiko
https://netdev-ai.bots.linux.dev/sashiko/#/message/20260824134703.766708-2-nb%40tipi-net.de:
Quoted 32 lines
--- Patch [1]: [PATCH net 1/2] net: macb: exclude software FCS from TX byte statistics ---
commit24acee751440b1a44c9e16688554df0848ab621a
Author: Nicolai Buchwitz <[email protected]>net: macb: exclude software FCS from TX byte statistics
Frames going through
macb_pad_and_fcs()get padded and four FCS bytes appended, and TX completion then accounts the grownskb->len.tx_bytesis supposed to exclude the FCS, and frames padded by the hardware are counted without the padding anyway, so these frames show up too large in the statistics.Quoted 5 lines
drivers/net/ethernet/cadence/macb_main.c +0
-0drivers/net/ethernet/cadence/macb_main.c static void macb_tx_error_task(struct work_struct *work) · line 1329
Quoted 10 lines
drivers/net/ethernet/cadence/macb_main.c +2
-2@@ -1322,8 +1322,8 @@ static void macb_tx_error_task(struct work_struct *work) bp->netdev->stats.tx_packets++; queue->stats.tx_packets++; packets++; - bp->netdev->stats.tx_bytes += skb->len; - queue->stats.tx_bytes += skb->len; + bp->netdev->stats.tx_bytes += tx_skb->skb_len; + queue->stats.tx_bytes += tx_skb->skb_len; bytes += skb->len; } }else {This is a pre-existing issue, but does
macb_tx_error_task()leak BQL bytes for dropped pending packets?
Quoted 8 lines
When recovering from a TX error,
macb_tx_error_task()iterates through the TX ring. For pending descriptors that did not successfully transmit, the code callsmacb_tx_unmap(bp, tx_skb, 0)which frees the SKB.However, it appears to fail to accumulate the freed SKB's length into the bytes accumulator. When
netdev_tx_completed_queue()is subsequently called, these leaked bytes are never reported to BQL, which could permanently retain these charged bytes and stall the TX queue.
Looks like it. The dropped frames never get a completion credit, and DQL only gets reset on close. This is independent of the statistics change, so I would address it in a follow-up fix. Objections?
Quoted 7 lines
This is another pre-existing issue, but does
macb_tx_error_task()modify the TX ring pointers without holding the appropriate lock?
macb_tx_error_task()acquiresbp->lockand issues a non-blocking stop to the queues vianetif_tx_stop_all_queues(). It then manipulates the ring pointersqueue->tx_headandqueue->tx_tail.
Quoted 7 lines
However, the fast-path
macb_start_xmit()protects these identical pointers usingqueue->tx_ptr_lock.Since
netif_tx_stop_all_queues()does not wait for an already-runningmacb_start_xmit()to complete, couldmacb_tx_error_task()zero out the ring pointers whilemacb_start_xmit()is concurrently populating descriptors on another CPU?
AFAIU yes, stopping the queues doesn't wait for a start_xmit that's already running. Taking tx_ptr_lock there before bp->lock, in the same order as start_xmit, should fix that. I would handle this together with the BQL issue in a follow-up series.
Quoted 11 lines
[ ... ]
drivers/net/ethernet/cadence/macb_main.c static netdev_tx_t macb_start_xmit(struct sk_buff *skb, · line 2491
Quoted 6 lines
drivers/net/ethernet/cadence/macb_main.c +1
-0@@ -2485,6 +2487,7 @@ static netdev_tx_t macb_start_xmit(struct sk_buff *skb,return ret; } + skb_len = skb->len;if (macb_pad_and_fcs (&skb, netdev)) {This isn't a bug introduced by this patch, but does
macb_pad_and_fcs()append an FCS before verifying TX ring space, which could corrupt the SKB upon retry?
Quoted 6 lines
[ ... ]
Because the network stack will subsequently retry transmitting this identical SKB, and its length is now larger, will
macb_pad_and_fcs()compute a new CRC over the old FCS and append a second, duplicate FCS, eventually corrupting the payload once tailroom is exhausted?
Yes, and the copy path looks worse: the stack can requeue an skb the driver already consumed. I'll do the ring space check before touching the skb at all. After that point the driver never returns NETDEV_TX_BUSY, so swapping the skb should be fine.
Quoted 7 lines
This is also a pre-existing issue, but does
macb_pad_and_fcs()modify shared SKB data for cloned packets and break nonlinear SKB layouts?If an SKB is cloned (e.g., multicast, TCP retransmissions) or nonlinear (paged fragments), and its length is already >=
ETH_ZLEN(60 bytes) so padlen <= 0, and it has at least 4 bytes of tailroom, the code skips the reallocation check:
Quoted 8 lines
if (padlen <= 0) { /* FCS could be appeded to tailroom. */ if (tailroom >= ETH_FCS_LEN) goto add_fcs;It then directly appends 4 bytes of FCS via
skb_put_u8(). For cloned SKBs, this modifies shared memory data. For nonlinear SKBs,skb_put()illegally extends the linear part, which could trigger a panic inskb_panic().
The cloned part looks right. The nonlinear case IMHO can't trigger today:skb_tailroom() is 0 for nonlinear skbs, so they go down skb_copy_expand(), which linearizes them anyway.
I'll order the cloned check before the in-place FCS path.
Paolo Abeni
maintainerRe: [PATCH net 1/2] net: macb: exclude software FCS from TX byte statistics
Quoted 2 lines · Nicolai Buchwitz
Replying to netdev's sashiko
https://netdev-ai.bots.linux.dev/sashiko/#/message/20260824134703.766708-2-nb%40tipi-net.de:
It looks like you instead replied to the comments from:
https://sashiko.dev/#/patchset/20260824134703.766708-1-nb%40tipi-net.de
Note that our reference saskiko instance is actually the one you pointed to above, even if the comments are at as slightly different URL:
https://netdev-ai.bots.linux.dev/sashiko/#/patchset/20260824134703.766708-1-nb%40tipi-net.de
Also note that pre-existing issue should (usually) not be addressed in the same patchset (unless really bad/exploitable).
Finally I have some concerns WRT patch 2/2: it should bring a significant performance regression, and the frames transmitted ATM are still valid (even if 'downgraded' csum wise). It would probably be good to provide some priv flag to enable/disable such behavior.
I guess some/most users would prefer send 1 frame out of 64K with csum validation unexpectedly disabled than hit a huge slowdown.
/P
Re: [PATCH net 1/2] net: macb: exclude software FCS from TX byte statistics
Hi Paolo
Quoted 6 lines · Paolo Abeni
Quoted 2 lines · Nicolai Buchwitz
Replying to netdev's sashiko
https://netdev-ai.bots.linux.dev/sashiko/#/message/20260824134703.766708-2-nb%40tipi-net.de:It looks like you instead replied to the comments from:
Quoted 7 lines
https://sashiko.dev/#/patchset/20260824134703.766708-1-nb%40tipi-net.de
Note that our reference saskiko instance is actually the one you pointed to above, even if the comments are at as slightly different URL:
https://netdev-ai.bots.linux.dev/sashiko/#/patchset/20260824134703.766708-1-nb%40tipi-net.de
Thanks for the pointer. I'll have another look and check the findings.
Only partially related, but is there a good way to c&p the sashiko review already quoted, so it is easier to respond inline via email? I saw the discussion about sending feedback via email and also the note from Jakub in the 7.2 stats that the current false positive rate _might_ be stable enough to do this in the future, but until then this would help a lot!
Quoted 3 lines
Also note that pre-existing issue should (usually) not be addressed in the same patchset (unless really bad/exploitable).
I've bundled patch 1 because patch 2 makes it far more visible. Happy to split out if you'd rather.
Quoted 5 lines
Finally I have some concerns WRT patch 2/2: it should bring a significant performance regression, and the frames transmitted ATM are still valid (even if 'downgraded' csum wise). It would probably be good to provide some priv flag to enable/disable such behavior.
Agreed. I'm currently testing another approach that checks whether the checksum would be 0 and only does the sw checksum calculation for those packets. Also, the testing from Alexander showed that maybe not all revisions are affected. Théo can probably check Mobileye silicon so we can pin this down further.
Quoted 3 lines
I guess some/most users would prefer send 1 frame out of 64K with csum validation unexpectedly disabled than hit a huge slowdown.
Agreed, lets see if the different approach might save us this at all.
Quoted 2 lines
/P
Cheers
Nicolai
Jakub Kicinski
maintainerRe: [PATCH net 1/2] net: macb: exclude software FCS from TX byte statistics
In reply to Nicolai BuchwitzQuoted 2 lines · On Mon, 24 Aug 2026 15:47:02 +0200 Nicolai Buchwitz wrote:
+ * @skb_len:
skb->lenas handed over by the stack, before padding and
+ * software FCS, only set for the last buffer of the frame
counting pad bytes to ETH_ZLEN as sent is perfectly legit, it's a driver preference. Some don't because HW pads and the driver doesn't want to bother adding a conditional. But it's best if the driver bytes match wire bytes IMO.
Either way, you only need u8 or even a flag for this, not a full u32?
Re: [PATCH net 1/2] net: macb: exclude software FCS from TX byte statistics
Hi Jakub
Quoted 8 lines · Jakub Kicinski
Quoted 2 lines · On Mon, 24 Aug 2026 15:47:02 +0200 Nicolai Buchwitz wrote:
+ * @skb_len:
skb->lenas handed over by the stack, before padding and
+ * software FCS, only set for the last buffer of the framecounting pad bytes to
ETH_ZLENas sent is perfectly legit, it's a driver preference. Some don't because HW pads and the driver doesn't want to bother adding a conditional. But it's best if the driver bytes match wire bytes IMO.
Matches what I had in mind for my v2. So the driver bytes would match wire bytes minus FCS.
Quoted 3 lines
Either way, you only need u8 or even a flag for this, not a full u32?
Agreed. skb->len at completion should already do the trick (minus ETH_FCS_LEN). So a flag would be sufficient.
Thanks,
Nicolai
Re: [PATCH net 1/2] net: macb: exclude software FCS from TX byte statistics
Quoted 16 lines · On Fri, 28 Aug 2026 10:20:24 +0200 Nicolai Buchwitz <[email protected]> wrote:
Hi Jakub
Quoted 8 lines · Jakub Kicinski
Quoted 2 lines · On Mon, 24 Aug 2026 15:47:02 +0200 Nicolai Buchwitz wrote:
+ * @skb_len:
skb->lenas handed over by the stack, before padding and
+ * software FCS, only set for the last buffer of the framecounting pad bytes to
ETH_ZLENas sent is perfectly legit, it's a driver preference. Some don't because HW pads and the driver doesn't want to bother adding a conditional. But it's best if the driver bytes match wire bytes IMO.Matches what I had in mind for my v2. So the driver bytes would match wire bytes minus FCS.
Quoted 1 line
Quoted 6 lines
Quoted 2 lines
Either way, you only need u8 or even a flag for this, not a full u32?
Agreed.
skb->lenat completion should already do the trick (minusETH_FCS_LEN).
So a flag would be sufficient.
If you make the 'flag' 0 or 4 it will save some maths (and maybe a branch) in the completion code.
David
Quoted 4 lines
Thanks,
Nicolai
Re: [PATCH net 1/2] net: macb: exclude software FCS from TX byte statistics
Hi David
Quoted 7 lines · David Laight
On Fri, 28 Aug 2026 10:20:24 +0200
[...]
Quoted 3 lines
Quoted 2 lines
Either way, you only need u8 or even a flag for this, not a full u32?
Quoted 6 lines
Quoted 3 lines
Agreed.
skb->lenat completion should already do the trick (minusETH_FCS_LEN).
So a flag would be sufficient.If you make the 'flag' 0 or 4 it will save some maths (and maybe a branch) in the completion code.
I will make tx_skb->fcs_len hold 0 or ETH_FCS_LEN directly, so completion becomes a skb->len - tx_skb->fcs_len. Anyway, I will split the patch into its own as suggested by Paolo and you.
Quoted 1 line
[...]
Thanks
Nicolai
Re: [PATCH net 1/2] net: macb: exclude software FCS from TX byte statistics
In reply to Jakub KicinskiQuoted 4 lines · On Thu, 27 Aug 2026 11:56:01 -0700 Jakub Kicinski <[email protected]> wrote:
Quoted 2 lines · On Mon, 24 Aug 2026 15:47:02 +0200 Nicolai Buchwitz wrote:
+ * @skb_len:
skb->lenas handed over by the stack, before padding and
+ * software FCS, only set for the last buffer of the frame
Quoted 8 lines
counting pad bytes to
ETH_ZLENas sent is perfectly legit, it's a driver preference. Some don't because HW pads and the driver doesn't want to bother adding a conditional. But it's best if the driver bytes match wire bytes IMO.Either way, you only need u8 or even a flag for this, not a full u32?
You could save a count to be subtracted from skb->len. But isn't that also unrelated to the UDP checksum issue?
Note that the receiver will treat an IPv4 checksum of zero as valid. For IPv6 it is a protocol error.
David
PATCH 2/2 net: macb: fix zero UDPv4 checksum on transmit
In reply to Nicolai BuchwitzThe GEM checksum engine writes its raw result into the UDP checksum field, so a UDPv4 checksum that computes to zero goes out as 0x0000. RFC 768 requires:
If the computed checksum is zero, it is transmitted as all ones (the equivalent in one's complement arithmetic). An all zero transmitted checksum value means that the transmitter generated no checksum (for debugging or for higher level protocols that don't care).
Raspberry Pi confirmed in a simulation of the Cadence IP [1] that the engine skips the final substitution exactly for UDP over IPv4. UDPv6 and TCP come out correct. The IP changelog shows no related change, so probably all GEM revisions have the same bug.
Clear the checksum offload features for UDPv4 frames in macb_features_check(), the core then completes the checksum in software. With ip_summed cleared, macb_pad_and_fcs() appends the FCS and TX_NOCRC keeps the hardware off the frame. TCP and UDPv6 keep the offload.
One-step PTP sync packets stay on the hardware path, the MAC rewrites their timestamp during transmit and would invalidate a software checksum.
--- drivers/net/ethernet/cadence/macb_main.c | 11 +++++++++++ 1 file changed, 11 insertions(+)
drivers/net/ethernet/cadence/macb_main.c +11 -0
@@ -14,6 +14,7 @@#include <linux/dma-mapping.h> #include <linux/etherdevice.h> #include <linux/firmware/xlnx-zynqmp.h> +#include <linux/if_vlan.h> #include <linux/inetdevice.h> #include <linux/init.h> #include <linux/interrupt.h>
@@ -2373,6 +2374,16 @@ static netdev_features_t macb_features_check(struct sk_buff *skb,unsigned int nr_frags, f;unsigned int hdrlen; +/* The GEM skips the RFC 768 substitution of 0xffff for a zero +* UDPv4 checksum, do those in software. One-step PTP sync frames +* stay on hardware, the MAC rewrites their timestamp in flight. +*/ +if (skb->ip_summed ==CHECKSUM_PARTIAL && +vlan_get_protocol (skb) ==htons (ETH_P_IP ) && + skb->csum_offset == offsetof(struct udphdr , check) && + !ptp_one_step_sync (skb)) + features &= ~NETIF_F_CSUM_MASK ; +/* Validate LSO compatibility */ /* there is only one buffer or protocol is not UDP */
Signature · 1 line
2.53.0
Hello Nicolai,
Am Mon, Aug 24, 2026 at 03:47:01PM +0200 schrieb Nicolai Buchwitz:
Quoted 32 lines
When a UDPv4 checksum computes to zero, RFC 768 wants
0xffffon the wire, but the GEM sends the raw0x0000, which receivers read as "no checksum". Raspberry Pi confirmed in a simulation of the Cadence IP that the engine skips the substitution for UDPv4. UDPv6 and TCP are fine, and the IP changelog suggests all GEM revisions could be affected. Reported and analyzed on the Raspberry Pi 5:
https://github.com/raspberrypi/linux/issues/7550Patch 2 does UDPv4 checksums in software and lets the existing pad and FCS path keep the hardware off the frame, UDPv6 and TCP keep the offload. That path miscounts
tx_bytesby the software FCS, so patch 1 fixes the accounting first.Tested on CM5. To reproduce, send bulk UDP to another host and capture zero checksums on the receiving side:
iperf3 -c <host> -u -b 200M -t 30
tcpdump -ni <iface> 'src host <dut> and udp[6:2] == 0'Without the fix a packet shows up every few seconds:
12:46:20.002739 IP <dut>.36309 > <host>.5201: UDP, length 1448 12:46:23.773968 IP <dut>.36309 > <host>.5201: UDP, length 1448 12:46:40.227460 IP <dut>.36309 > <host>.5201: UDP, length 1448
With the fix the capture showed none.
Some numbers (
udpgso_bench):
- 18-byte UDP throughput dropped by ~ 8%
- 256-byte UDP throughput dropped by ~ 10%
- MTU-sized UDP and UDP GSO were unchanged at the 116 MiB/s link limit
Quoted 5 lines
Unfortunately I don't see a cheaper fix, the zero only shows up after computing the checksum, the MAC inserts it in flight, and AFAIU there is no register or descriptor bit for the substitution.
I'd appreciate testing on other silicon.
I tested without your patch on at91 sama5d2 (Cadence GEM rev 0x00020203), sam9x60 (Cadence MACB rev 0x0001010c), and sam9g20 (Cadence MACB rev 0x0001010c), and tried to reproduce the flaw (not the fix). Rewrote the Python reproducer suggested in that RPi github issue in C, but iperf3 gave similar results: tcpdump started as suggested showed not a single wrong package!
However according to ethtool it seems at least the older MACB bases hardware has no hardware checksumming here. On sama5d2 (GEM, but no Gigabit) I'm not sure if it is supposed to be done for UDP? See:
$ ethtool -k eth0 | grep sum
rx-checksumming: on
tx-checksumming: on
tx-checksum-ipv4: off [fixed]
tx-checksum-ip-generic: on
tx-checksum-ipv6: off [fixed]
tx-checksum-fcoe-crc: off [fixed]
tx-checksum-sctp: off [fixed]
tx-gre-csum-segmentation: off [fixed]
tx-udp_tnl-csum-segmentation: off [fixed]
tx-tunnel-remcsum-segmentation: off [fixed]
esp-tx-csum-hw-offload: off [fixed]On sam9x60 (MACB) there seems to be no hardware offloading at all:
$ ethtool -k eth0 | grep sum
rx-checksumming: off [fixed]
tx-checksumming: off
tx-checksum-ipv4: off [fixed]
tx-checksum-ip-generic: off [fixed]
tx-checksum-ipv6: off [fixed]
tx-checksum-fcoe-crc: off [fixed]
tx-checksum-sctp: off [fixed]
tx-gre-csum-segmentation: off [fixed]
tx-udp_tnl-csum-segmentation: off [fixed]
tx-tunnel-remcsum-segmentation: off [fixed]
esp-tx-csum-hw-offload: off [fixed]How are those chips affected by your patch then?
Quoted 3 lines
Nicolai Buchwitz (2):
net: macb: exclude software FCS from TX byte statistics
net: macb: fix zero UDPv4 checksum on transmit
That fix seems to be very generic and not specific to macb or gem nor to any variant. I'd suggest narrowing it down and testing on more hardware.
Greets
Alex
Quoted 8 lines
drivers/net/ethernet/cadence/macb.h | 3 +++ drivers/net/ethernet/cadence/macb_main.c | 28 +++++++++++++++++++++------- 2 files changed, 24 insertions(+), 7 deletions(-)Signature · 1 line
2.53.0