From: Gerrit Renker <gerrit@erg.abdn.ac.uk>
To: davem@davemloft.net, dccp@vger.kernel.org, netdev@vger.kernel.org
Subject: [pull-request] [net-2.6 PATCH 0/6] dccp: Revised ICMP / length fixes
Date: Sat, 26 Jul 2008 12:22:33 +0100 [thread overview]
Message-ID: <20080726112232.GA5582@gerrit.erg.abdn.ac.uk> (raw)
In-Reply-To: <20080725142834.GA7422@gerrit.erg.abdn.ac.uk>
Hi Dave,
this is an update on yesterday's submission, which was unnecessarily complex.
I have checked the whole set again and looked through dccp_invalid_packet()
in net/dccp/ipv4.c. There is no need for additional protection: the routine
makes sure that the skb is long enough for the Data Offset (header length),
which is more than the __dccp_basic_hdr_len().
The ICMPv4/6 packet length checks now in effect use the two-stage test you
suggested, to ensure that the ICMP payload is long enough to access the
first 12 bytes that __dccp_basic_hdr_len() dereferences.
Please let me know if individual patches should be resubmitted again.
I have not done this to reduce noise; in any case the changes are also online:
http://eden-feed.erg.abdn.ac.uk/cgi-bin/gitweb.cgi?p=net-2.6.git;a=log
Patch #1: Implements support to distinguish original from retransmitted packets.
Patch #2: Fixes a bug - AWL was never updated. Used by the third patch.
Patch #3: Corrects ICMPv4 sequence number check to use AWL/H instead of SWL/H.
Patch #4: Implements the check from patch #3 for ICMPv6.
Patch #5: Fixes minimum-required length check for ICMPv4 embedded DCCP datagrams
Patch #6: Same as patch #5, but for ICMPv6.
These patches apply to net-2.6 (BUG_TRAP conversion) and can be pulled from
git://eden-feed.erg.abdn.ac.uk/net-2.6 (subtree `master')
If necessary, I can prepare an upload for net-next-2.6 later.
Gerrit
next prev parent reply other threads:[~2008-07-26 11:22 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <dccp_icmp_payload_bug_fixes>
2008-07-25 9:02 ` [net-2.6 PATCH 0/6] dccp: ICMP bug fixes by Wei Yongjun Gerrit Renker
2008-07-25 9:02 ` [PATCH 1/6] dccp: Allow to distinguish original and retransmitted packets Gerrit Renker
2008-07-25 9:02 ` [PATCH 2/6] dccp: Bug-Fix - AWL was never updated Gerrit Renker
2008-07-25 9:02 ` [PATCH 3/6] dccp: Fix sequence number check for ICMPv4 packets Gerrit Renker
2008-07-25 9:02 ` [PATCH 4/6] dccp: Add check for sequence number in ICMPv6 message Gerrit Renker
2008-07-25 9:02 ` [PATCH 5/6] dccp: Fix incorrect length check for ICMPv4 packets Gerrit Renker
2008-07-25 9:02 ` [PATCH 6/6] dccp: Add check for truncated ICMPv6 DCCP error packets Gerrit Renker
2008-07-25 9:51 ` [PATCH 5/6] dccp: Fix incorrect length check for ICMPv4 packets David Miller
2008-07-25 10:25 ` Gerrit Renker
2008-07-25 9:52 ` [net-2.6 PATCH 0/6] dccp: ICMP bug fixes by Wei Yongjun David Miller
2008-07-25 14:28 ` v2 [net-2.6 PATCH 0-4/7] dccp: Revised ICMP bug fixes Gerrit Renker
2008-07-25 14:29 ` [PATCH 5/7] dccp: Pulling 12 bytes is necessary but not sufficient Gerrit Renker
2008-07-25 14:30 ` v2 [PATCH 6/7] dccp: Fix incorrect length check for ICMPv4 packets Gerrit Renker
2008-07-25 14:31 ` v2 [PATCH 7/7] dccp: Add check for truncated ICMPv6 DCCP error packets Gerrit Renker
2008-07-26 11:22 ` Gerrit Renker [this message]
2008-07-27 12:03 ` [pull-request] [net-2.6 PATCH 0/6] dccp: Revised ICMP / length fixes David Miller
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=20080726112232.GA5582@gerrit.erg.abdn.ac.uk \
--to=gerrit@erg.abdn.ac.uk \
--cc=davem@davemloft.net \
--cc=dccp@vger.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 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).