netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Eric Brower <ebrower@usa.net>
To: netdev@oss.sgi.com, linux@syskonnect.de
Subject: [PATCH] sk98lin hardware rx csum offload logic
Date: Wed, 16 Feb 2005 11:38:24 -0800	[thread overview]
Message-ID: <4213A130.8070909@usa.net> (raw)

[-- Attachment #1: Type: text/plain, Size: 702 bytes --]

The sk98lin driver drops received packets that have an invalid 
IP/UDP/TCP checksum-- it should be passing these packets up the stack by 
marking the skb's ip_summed to CHECKSUM_NONE rather than simply dropping 
them (ref. 
http://efault.net/npat/docs_and_postings/net_device-features/net_device-features.txt 
and other network driver implementations)

Attached is a patch against the latest BK 2.6 kernel.  This issue also 
applies to 2.4 and the latest version of the driver (8.13.1.3) on the 
SysKonnect site, though in that case a similar fix needs to be made to 
the sky2.c Yukon2 support.

I'm not on the netdev list, so if there is any further discussion please 
include me directly.

Thanks,
E

[-- Attachment #2: sk98lin_hwrxcsum.patch --]
[-- Type: text/plain, Size: 524 bytes --]

===== drivers/net/sk98lin/skge.c 1.54 vs edited =====
--- 1.54/drivers/net/sk98lin/skge.c	2004-11-03 14:31:05 -08:00
+++ edited/drivers/net/sk98lin/skge.c	2005-02-16 09:14:02 -08:00
@@ -2254,8 +2254,8 @@
 							/* HW Checksum error */
 							SK_DBG_MSG(NULL, SK_DBGMOD_DRV,
 							SK_DBGCAT_DRV_RX_PROGRESS,
-							("skge: CRC error. Frame dropped!\n"));
-							goto rx_failed;
+							("skge: CRC error.\n"));
+							pMsg->ip_summed = CHECKSUM_NONE;
 						} else {
 								pMsg->ip_summed =
 								CHECKSUM_NONE;

                 reply	other threads:[~2005-02-16 19:38 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=4213A130.8070909@usa.net \
    --to=ebrower@usa.net \
    --cc=linux@syskonnect.de \
    --cc=netdev@oss.sgi.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).