From: Brian Haley <brian.haley@hp.com>
To: Shan Wei <shanwei@cn.fujitsu.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: Wed, 03 Sep 2008 14:36:46 -0400 [thread overview]
Message-ID: <48BED93E.2000204@hp.com> (raw)
In-Reply-To: <48BE4DA2.20800@cn.fujitsu.com>
Shan Wei wrote:
> I'm sorry to resend the patch, for that no one replied it from Jun 27.
>
> The kernel had removed the RH0(Type 0 Routing Header), but we can still
> send IPv6 packet with RH0 using sendmsg() or setsockopt().
>
> Compare with sendmsg() that returns EINVAL, but setsockopt() return EPERM.
> The patch fix it.
>
> Signed-off-by: Shan Wei <shanwei@cn.fujitsu.com>
> ---
> net/ipv6/ipv6_sockglue.c | 6 ++++--
> 1 files changed, 4 insertions(+), 2 deletions(-)
>
> diff --git a/net/ipv6/ipv6_sockglue.c b/net/ipv6/ipv6_sockglue.c
> index 4e5eac3..7a58597 100644
> --- a/net/ipv6/ipv6_sockglue.c
> +++ b/net/ipv6/ipv6_sockglue.c
> @@ -353,9 +353,10 @@ static int do_ipv6_setsockopt(struct sock *sk, int level, int optname,
> goto e_inval;
>
> /* hop-by-hop / destination options are privileged option */
> - retv = -EPERM;
> - if (optname != IPV6_RTHDR && !capable(CAP_NET_RAW))
> + if (optname != IPV6_RTHDR && !capable(CAP_NET_RAW)) {
> + retv = -EPERM;
> break;
> + }
I'm not sure you need this since it doesn't actually change anything,
setting the error before the check just seems like the style in this
function. It will get set to -EINVAL below...
> @@ -365,6 +366,7 @@ static int do_ipv6_setsockopt(struct sock *sk, int level, int optname,
> break;
> }
>
> + retv = -EINVAL;
> /* routing header option needs extra check */
> if (optname == IPV6_RTHDR && opt && opt->srcrt) {
> struct ipv6_rt_hdr *rthdr = opt->srcrt;
This seems correct as trying to set an unsupported routing header type
is invalid, or trying to set a Type 2 that itself is invalid is bad.
The Unix I checked does this.
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.
-Brian
next prev parent reply other threads:[~2008-09-03 18:36 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 [this message]
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
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=48BED93E.2000204@hp.com \
--to=brian.haley@hp.com \
--cc=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=shanwei@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).