From: Hagen Paul Pfeifer <hagen@jauu.net>
To: dccp@vger.kernel.org
Subject: [PATCH] Mandatory Option Draft Cleanup
Date: Tue, 28 Feb 2006 20:15:05 +0000 [thread overview]
Message-ID: <20060228201505.GD317@c3po.0xdef.net> (raw)
In-Reply-To: <20060222113802.GB21876@c3po.0xdef.net>
[-- Attachment #1: Type: text/plain, Size: 481 bytes --]
According to dccp draft (draft-ietf-dccp-spec-13.txt) section 5.8.2 (Mandatory
Option) the following patch correct the handling of the following cases:
1) "... and any Mandatory options received on DCCP-Data packets MUST be
ignored."
2) "The connection is in error and should be reset with Reset Code 5, ...
if option O is absent (Mandatory was the last byte of the option list), or
if option O equals Mandatory."
Signed-off-by: Hagen Paul Pfeifer <hagen@jauu.net>
[-- Attachment #2: mandatory.patch --]
[-- Type: text/plain, Size: 635 bytes --]
diff --git a/net/dccp/options.c b/net/dccp/options.c
index 7d73b33..3db9aad 100644
--- a/net/dccp/options.c
+++ b/net/dccp/options.c
@@ -107,7 +107,8 @@ int dccp_parse_options(struct sock *sk,
case DCCPO_MANDATORY:
if (mandatory)
goto out_invalid_option;
- mandatory = 1;
+ if (pkt_type != DCCP_PKT_DATA)
+ mandatory = 1;
break;
case DCCPO_NDP_COUNT:
if (len > 3)
@@ -247,6 +248,10 @@ int dccp_parse_options(struct sock *sk,
mandatory = 0;
}
+ /* mandatory was the last byte in option list -> reset connection */
+ if (mandatory)
+ goto out_invalid_option;
+
return 0;
out_invalid_option:
next prev parent reply other threads:[~2006-02-28 20:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-22 11:38 [PATCH] Mandatory Option Draft Cleanup Hagen Paul Pfeifer
2006-02-28 20:15 ` Hagen Paul Pfeifer [this message]
2006-02-28 20:28 ` Arnaldo Carvalho de Melo
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=20060228201505.GD317@c3po.0xdef.net \
--to=hagen@jauu.net \
--cc=dccp@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