All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Tan Tee Min <tee.min.tan@linux.intel.com>
Cc: stable@vger.kernel.org
Subject: Re: [PATCH] net: stmmac: disable Split Header (SPH) for Intel platforms
Date: Mon, 23 May 2022 17:14:17 +0200	[thread overview]
Message-ID: <YoukydQZAds2Lazf@kroah.com> (raw)
In-Reply-To: <20220523013910.3147844-1-tee.min.tan@linux.intel.com>

On Mon, May 23, 2022 at 09:39:10AM +0800, Tan Tee Min wrote:
> commit 47f753c1108e287edb3e27fad8a7511a9d55578e upstream.
> 
> Based on DesignWare Ethernet QoS datasheet, we are seeing the limitation
> of Split Header (SPH) feature is not supported for Ipv4 fragmented packet.
> This SPH limitation will cause ping failure when the packets size exceed
> the MTU size. For example, the issue happens once the basic ping packet
> size is larger than the configured MTU size and the data is lost inside
> the fragmented packet, replaced by zeros/corrupted values, and leads to
> ping fail.
> 
> So, disable the Split Header for Intel platforms.
> 
> v2: Add fixes tag in commit message.
> 
> Fixes: 67afd6d1cfdf("net: stmmac: Add Split Header support and enable it in XGMAC cores")
> Cc: <stable@vger.kernel.org> # 5.4.x
> Suggested-by: Ong, Boon Leong <boon.leong.ong@intel.com>
> Signed-off-by: Mohammad Athari Bin Ismail <mohammad.athari.ismail@intel.com>
> Signed-off-by: Wong Vee Khee <vee.khee.wong@linux.intel.com>
> Signed-off-by: Tan Tee Min <tee.min.tan@linux.intel.com>
> Signed-off-by: David S. Miller <davem@davemloft.net>
> ---
>  drivers/net/ethernet/stmicro/stmmac/stmmac_main.c | 2 +-
>  drivers/net/ethernet/stmicro/stmmac/stmmac_pci.c  | 1 +
>  include/linux/stmmac.h                            | 1 +
>  3 files changed, 3 insertions(+), 1 deletion(-)

Now queued up, thanks.

greg k-h

      reply	other threads:[~2022-05-23 15:14 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-23  1:39 [PATCH] net: stmmac: disable Split Header (SPH) for Intel platforms Tan Tee Min
2022-05-23 15:14 ` Greg KH [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=YoukydQZAds2Lazf@kroah.com \
    --to=greg@kroah.com \
    --cc=stable@vger.kernel.org \
    --cc=tee.min.tan@linux.intel.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.