From: Shan Wei <shanwei@cn.fujitsu.com>
To: Brian Haley <brian.haley@hp.com>
Cc: davem@davemloft.net, netdev@vger.kernel.org
Subject: Re: [PATCH RESEND] ipv6: return with appropriate error code when sending RH0 using setsockopt()
Date: Thu, 04 Sep 2008 13:53:23 +0800 [thread overview]
Message-ID: <48BF77D3.5010105@cn.fujitsu.com> (raw)
In-Reply-To: <48BED93E.2000204@hp.com>
Brian Haley 写道:
> Shan Wei wrote:
...snip...
> There's actually another bug here and in the sendmsg() path in that you
> can set the hdrlen and segments_left fields to be invalid (according to
> RFC3775), as long as the math works out (segments * 2 == length).
> Segments_left should always be 1 and hdrlen 2 for a Type2 routing
> header. The packet should be dropped at the destination, but we
> probably shouldn't send it. I can send a patch for that later.
>
I check the RFC3775. May be the following patch is good to you.
Signed-off-by: Shan Wei <shanwei@cn.fujitsu.com>
---
net/ipv6/datagram.c | 8 ++++++--
net/ipv6/ipv6_sockglue.c | 7 +++++--
2 files changed, 11 insertions(+), 4 deletions(-)
diff --git a/net/ipv6/datagram.c b/net/ipv6/datagram.c
index 410046a..cfd499a 100644
--- a/net/ipv6/datagram.c
+++ b/net/ipv6/datagram.c
@@ -675,8 +675,12 @@ int datagram_send_ctl(struct net *net,
goto exit_f;
}
- /* segments left must also match */
- if ((rthdr->hdrlen >> 1) != rthdr->segments_left) {
+ /* Per RFC3775, for a type 2 routing header,
+ * the Hdr Ext Len MUST be 2 and the Segments Left
+ * MUST be 1.
+ */
+ if ((rthdr->hdrlen != 2) &&
+ (rthdr->segments_left != 1)) {
err = -EINVAL;
goto exit_f;
}
diff --git a/net/ipv6/ipv6_sockglue.c b/net/ipv6/ipv6_sockglue.c
index 4e5eac3..b967965 100644
--- a/net/ipv6/ipv6_sockglue.c
+++ b/net/ipv6/ipv6_sockglue.c
@@ -377,8 +377,11 @@ static int do_ipv6_setsockopt(struct sock *sk, int level, int optname,
goto sticky_done;
}
- if ((rthdr->hdrlen & 1) ||
- (rthdr->hdrlen >> 1) != rthdr->segments_left)
+ /* Per RFC3775, for a type 2 routing header,
+ * the Hdr Ext Len MUST be 2 and the Segments Left
+ * MUST be 1.
+ */
+ if ((rthdr->hdrlen != 2) && (rthdr->segments_left != 1))
goto sticky_done;
}
--
1.6.0
next prev parent reply other threads:[~2008-09-04 5:55 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-03 8:41 [PATCH RESEND] ipv6: return with appropriate error code when sending RH0 using setsockopt() Shan Wei
2008-09-03 9:23 ` David Miller
2008-09-03 9:41 ` Shan Wei
2008-09-03 18:36 ` Brian Haley
2008-09-04 3:44 ` Shan Wei
2008-09-12 3:14 ` David Miller
2008-09-16 7:13 ` Shan Wei
2008-09-04 5:53 ` Shan Wei [this message]
2008-09-04 13:54 ` Brian Haley
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=48BF77D3.5010105@cn.fujitsu.com \
--to=shanwei@cn.fujitsu.com \
--cc=brian.haley@hp.com \
--cc=davem@davemloft.net \
--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.