netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Brian Haley <Brian.Haley@hp.com>
To: "YOSHIFUJI Hideaki / 吉藤英明" <yoshfuji@linux-ipv6.org>
Cc: davem@davemloft.net, netdev@vger.kernel.org
Subject: Re: [GIT PULL net-2.6] IPv6 fixes.
Date: Tue, 03 Jun 2008 21:19:44 -0400	[thread overview]
Message-ID: <4845EDB0.7030809@hp.com> (raw)
In-Reply-To: <20080604.094917.75827853.yoshfuji@linux-ipv6.org>

YOSHIFUJI Hideaki / 吉藤英明 wrote:
> Please consider pulling following fixes on top of net-2.6 tree
> available at
> 	git://git.linux-ipv6.org/gitroot/yoshfuji/linux-2.6-fix.git net-2.6-misc-20080604b
> 
...
> commit c878bc2da63acd3b80ba4cf428702f6e98c55b3c
> Author: YOSHIFUJI Hideaki <yoshfuji@linux-ipv6.org>
> Date:   Mon Jun 2 18:45:23 2008 +0900
> 
>     [IPv6]: Check outgoing interface even if source address is unspecified.
>     
>     The outgoing interface index (ipi6_ifindex) in IPV6_PKTINFO
>     ancillary data, is not checked if the source address (ipi6_addr)
>     is unspecified.  If the ipi6_ifindex is the not-exist interface,
>     it should be fail and the errno should be set ENODEV.
>     
>     Based on patch from Shan Wei <shanwei@cn.fujitsu.com>.
>     
>     Signed-off-by: Shan Wei <shanwei@cn.fujitsu.com>
>     Signed-off-by: YOSHIFUJI Hideaki <yoshfuji@linux-ipv6.org>
> 
> diff --git a/net/ipv6/datagram.c b/net/ipv6/datagram.c
> index 94fa6ae..76d4ab4 100644
> --- a/net/ipv6/datagram.c
> +++ b/net/ipv6/datagram.c
> @@ -535,27 +535,29 @@ int datagram_send_ctl(struct msghdr *msg, struct flowi *fl,
>  				fl->oif = src_info->ipi6_ifindex;
>  			}
>  
> -			addr_type = ipv6_addr_type(&src_info->ipi6_addr);
> +			if (fl->oif) {
> +				dev = dev_get_by_index(&init_net, fl->oif);
> +				if (!dev)
> +					return -ENODEV;
> +			}
>  
> -			if (addr_type == IPV6_ADDR_ANY)
> +			addr_type = ipv6_addr_type(&src_info->ipi6_addr);
> +			if (addr_type == IPV6_ADDR_ANY) {
> +				if (dev)
> +					dev_put(dev);
>  				break;
> -
> -			if (addr_type & IPV6_ADDR_LINKLOCAL) {
> -				if (!src_info->ipi6_ifindex)
> -					return -EINVAL;
> -				else {
> -					dev = dev_get_by_index(&init_net, src_info->ipi6_ifindex);
> -					if (!dev)
> -						return -ENODEV;
> -				}
>  			}
> -			if (!ipv6_chk_addr(&init_net, &src_info->ipi6_addr,
> +
> +			if (((addr_type & IPV6_ADDR_LINKLOCAL) &&
> +			     !src_info->ipi6_ifindex) ||
> +			    !ipv6_chk_addr(&init_net, &src_info->ipi6_addr,

I think this !src_info->ipi6_ifindex here should be !fl->oif - that will 
have been assigned correctly if it was zero and src_info->ipi6_ifindex 
was passed-in, and is what we used to do the device lookup.

-Brian

  reply	other threads:[~2008-06-04  1:22 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-04  0:49 [GIT PULL net-2.6] IPv6 fixes YOSHIFUJI Hideaki / 吉藤英明
2008-06-04  1:19 ` Brian Haley [this message]
2008-06-04  2:24   ` YOSHIFUJI Hideaki / 吉藤英明
2008-06-04  2:27   ` Shan Wei
2008-06-04  2:37     ` YOSHIFUJI Hideaki / 吉藤英明
2008-06-04  3:02       ` YOSHIFUJI Hideaki / 吉藤英明
2008-06-04  3:37         ` Shan Wei
2008-06-04 18:33           ` Brian Haley
2008-06-04 19:17             ` YOSHIFUJI Hideaki / 吉藤英明

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=4845EDB0.7030809@hp.com \
    --to=brian.haley@hp.com \
    --cc=davem@davemloft.net \
    --cc=netdev@vger.kernel.org \
    --cc=yoshfuji@linux-ipv6.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).