From: Shan Wei <shanwei@cn.fujitsu.com>
To: Yang Hongyang <yanghy@cn.fujitsu.com>
Cc: "netdev@vger.kernel.org" <netdev@vger.kernel.org>,
David Miller <davem@davemloft.net>,
brian.haley@hp.com
Subject: Re: [PATCH]ipv6:remove useless check
Date: Tue, 14 Apr 2009 11:31:40 +0800 [thread overview]
Message-ID: <49E4039C.5080908@cn.fujitsu.com> (raw)
In-Reply-To: <49E3EC04.5000105@cn.fujitsu.com>
Yang Hongyang said:
> After switch (rthdr->type) {...},the check below is completely useless.Because:
> if the type is 2,then hdrlen must be 2 and segments_left must be 1,clearly the
> check is redundant;if the type is not 2,then goto sticky_done,the check is useless
> too.
>
Add CC Brian Haley.
The check is defined only for Type 0 Routing header in section 4.4 of RFC2460:
Hdr Ext Len 8-bit unsigned integer. Length of the Routing
header in 8-octet units, not including the first
8 octets. For the Type 0 Routing header, Hdr
Ext Len is equal to two times the number of
addresses in the header.
Now, Type 0 Routing header has been removed, the check is redundant.
Reviewed-by: Shan Wei <shanwei@cn.fujitsu.com>
> Signed-off-by: Yang Hongyang <yanghy@cn.fujitsu.com>
>
> ---
> net/ipv6/ipv6_sockglue.c | 4 ----
> 1 files changed, 0 insertions(+), 4 deletions(-)
>
> diff --git a/net/ipv6/ipv6_sockglue.c b/net/ipv6/ipv6_sockglue.c
> index d31df0f..a7fdf9a 100644
> --- a/net/ipv6/ipv6_sockglue.c
> +++ b/net/ipv6/ipv6_sockglue.c
> @@ -380,10 +380,6 @@ static int do_ipv6_setsockopt(struct sock *sk, int level, int optname,
> default:
> goto sticky_done;
> }
> -
> - if ((rthdr->hdrlen & 1) ||
> - (rthdr->hdrlen >> 1) != rthdr->segments_left)
> - goto sticky_done;
> }
>
> retv = 0;
--
Best Regards
Shan Wei
next prev parent reply other threads:[~2009-04-14 3:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-14 1:51 [PATCH]ipv6:remove useless check Yang Hongyang
2009-04-14 3:31 ` Shan Wei [this message]
2009-04-14 9:22 ` 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=49E4039C.5080908@cn.fujitsu.com \
--to=shanwei@cn.fujitsu.com \
--cc=brian.haley@hp.com \
--cc=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=yanghy@cn.fujitsu.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).