From: Simon Horman <horms@kernel.org>
To: James <aslan.jnn@gmail.com>
Cc: Raju Rangoju <Raju.Rangoju@amd.com>,
Prashanth Kumar K R <PrashanthKumar.K.R@amd.com>,
netdev@vger.kernel.org, Thomas.Lendacky@amd.com,
Jakub Kicinski <kuba@kernel.org>
Subject: Re: [PATCH net v2] net: amd-xgbe: support receiving packets with bad FCS
Date: Fri, 21 Aug 2026 11:39:24 +0100 [thread overview]
Message-ID: <20260821103924.GH265046@horms.kernel.org> (raw)
In-Reply-To: <20260819091656.23943-1-aslan.jnn@gmail.com>
On Wed, Aug 19, 2026 at 07:16:56PM +1000, James wrote:
> amd-xgbe driver currently sets the MAC_RCR.DCRCC bit whenever RX is
> enabled. This disables hardware FCS validation, causing packets with
> bad FCS to be accepted unconditionally.
>
> This change unsets DCRCC so that packets with bad FCS will be dropped,
> in-line with typical behaviours of many other network controllers.
>
> Tests:
> - Verified that packets with bad FCS are now dropped.
> - Verified that receiving packets with bad FCS will increment the
> `rx_crc_errors` counter.
>
Hi James,
I think this warrants a fixes tag
(no blank line between it and your signed-off-by line).
Fixes: c5aa9e3b8156 ("amd-xgbe: Initial AMD 10GbE platform driver")
> Signed-off-by: James Nugraha <aslan.jnn@gmail.com>
net:amd-xgbe: discard rx packets with bad FCS
> ---
> Changes in v2:
> - Eliminated DCRCC toggling via RXALL: now it simply sets the
> correct default value on MAC Rx enable
> drivers/net/ethernet/amd/xgbe/xgbe-dev.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
I think you may have forgotten to update the patch description
as per the suggestion made by David in his review of v1.
net: amd-xgbe: discard rx packets with bad FCS
And, some points on process:
* Please post updated versions of patches
as separate threads rather than as respones to earlier versions.
* Please make sure the author of the patch matches the signed off by line.
You can do this by updating the from address in the email. Or
if that is not possible add an extra From: line at exactly
the first line of the body of the email.
Thanks!
--
pw-bot: changes-requested
next prev parent reply other threads:[~2026-08-21 10:39 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-12 9:16 [PATCH net] net: amd-xgbe: support receiving packets with bad FCS James
2026-08-14 10:09 ` Simon Horman
2026-08-19 2:36 ` James
2026-08-19 9:01 ` Simon Horman
2026-08-17 23:32 ` Jakub Kicinski
2026-08-19 6:31 ` James
2026-08-19 9:16 ` [PATCH net v2] " James
2026-08-21 10:39 ` Simon Horman [this message]
2026-08-19 11:43 ` [PATCH net] " David Laight
2026-08-20 0:38 ` James
2026-08-20 8:58 ` David Laight
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=20260821103924.GH265046@horms.kernel.org \
--to=horms@kernel.org \
--cc=PrashanthKumar.K.R@amd.com \
--cc=Raju.Rangoju@amd.com \
--cc=Thomas.Lendacky@amd.com \
--cc=aslan.jnn@gmail.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
/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.