netdev - [PATCH] net/ipv4: Correct RFC 1122 section reference in comment

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <20080507072423.GA13556@xinara.org>
Date:	Wed, 7 May 2008 09:24:23 +0200
From:	"J.H.M. Dassen (Ray)" <jdassen@...ian.org>
To:	Andrew Morton <akpm@...ux-foundation.org>
Cc:	netdev@...r.kernel.org, trivial@...nel.org
Subject: [PATCH] net/ipv4: Correct RFC 1122 section reference in comment

From: J.H.M. Dassen (Ray) <jdassen@...ian.org>

RFC 1122 does not have a section 3.1.2.2. The requirement to silently
discard datagrams with a bad checksum is in section 3.2.1.2 instead.

Signed-off-by: J.H.M. Dassen (Ray) <jdassen@...ian.org>

---

Previously submitted as http://bugzilla.kernel.org/show_bug.cgi?id=10611

diff --git a/net/ipv4/ip_input.c b/net/ipv4/ip_input.c
index 212734c..5bdb8f4 100644
--- a/net/ipv4/ip_input.c
+++ b/net/ipv4/ip_input.c
@@ -394,7 +394,7 @@ int ip_rcv(struct sk_buff *skb, struct net_device *dev, struct packet_type *pt,
 	iph = skb->nh.iph;

 	/*
-	 *	RFC1122: 3.1.2.2 MUST silently discard any IP frame that fails the checksum.
+	 *	RFC1122: 3.2.1.2 MUST silently discard any IP frame that fails the checksum.
 	 *
 	 *	Is the datagram acceptable?
 	 *

-- 
LEADERSHIP  A form of self-preservation exhibited by people with auto-
destructive imaginations in order to ensure that when it comes to the crunch
it'll be someone else's bones which go crack and not their own.
    - The Hipcrime Vocab by Chad C. Mulligan
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html