sfc: Pad packets to 33 bytes to prevent TX packet parser lockup

The packet parser used in the TX data path for locating checksum
fields can lose synchronisation with the TX queue manager when
handling packets that look like IPv4 but are too short (17-32 bytes).
Work around this by padding to 33 bytes.

Signed-off-by: Ben Hutchings <bhutchings@solarflare.com>
Signed-off-by: David S. Miller <davem@davemloft.net>

1 files changed, 8 insertions, 0 deletions

diff --git a/drivers/net/sfc/tx.c b/drivers/net/sfc/tx.c
index b1e190779073..d6681edb7014 100644
--- a/drivers/net/sfc/tx.c
+++ b/drivers/net/sfc/tx.c
@@ -162,6 +162,14 @@ static int efx_enqueue_skb(struct efx_tx_queue *tx_queue,
         /* Get size of the initial fragment */
         len = skb_headlen(skb);
 
+        /* Pad if necessary */
+        if (EFX_WORKAROUND_15592(efx) && skb->len <= 32) {
+                EFX_BUG_ON_PARANOID(skb->data_len);
+                len = 32 + 1;
+                if (skb_pad(skb, len - skb->len))
+                        return NETDEV_TX_OK;
+        }
+
         fill_level = tx_queue->insert_count - tx_queue->old_read_count;
         q_space = efx->type->txd_ring_mask - 1 - fill_level;