linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Matthias Andree <matthias.andree@stud.uni-dortmund.de>
To: jamal <hadi@cyberus.ca>
Cc: linux-kernel@vger.kernel.org, netdev@oss.sgi.com,
	Andi Kleen <ak@muc.de>,
	kuznet@ms2.inr.ac.ru
Subject: Re: ioctl SIOCGIFNETMASK: ip alias bug 2.4.9 and 2.2.19
Date: Thu, 6 Sep 2001 22:22:28 +0200	[thread overview]
Message-ID: <20010906222228.I13547@emma1.emma.line.org> (raw)
In-Reply-To: <Pine.GSO.4.30.0109051803500.11700-100000@shell.cyberus.ca>
In-Reply-To: <Pine.GSO.4.30.0109051803500.11700-100000@shell.cyberus.ca>

On Wed, 05 Sep 2001, jamal wrote:

> --- devinet.c   2001/09/04 19:18:51     1.1
> +++ devinet.c   2001/09/04 19:31:13
> @@ -530,7 +530,7 @@
> 
>         if ((in_dev=__in_dev_get(dev)) != NULL) {
>                 for (ifap=&in_dev->ifa_list; (ifa=*ifap) != NULL;
> ifap=&ifa->ifa_next)
> -                       if (strcmp(ifr.ifr_name, ifa->ifa_label) == 0)
> +                       if ((strcmp(ifr.ifr_name, ifa->ifa_label) == 0) ||
> (sin->sin_addr.s_addr == ifa->ifa_address))
>                                 break;
>         }

Thanks for trying to help, however, that's not going to work this way, sorry.

1. "sin" is cleared a few lines above, so you end up comparing 0.0.0.0
   against "ifa->ifa_address".

2. two interfaces can have the same configured address, your patch might
   end up returning the wrong address. You'd need to write && where you
   wrote ||, and you'd need to save the old address.

See the patch that I sent.

-- 
Matthias Andree

  parent reply	other threads:[~2001-09-06 20:35 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-09-05 22:08 ioctl SIOCGIFNETMASK: ip alias bug 2.4.9 and 2.2.19 jamal
2001-09-06 15:11 ` kuznet
2001-09-06 20:22 ` Matthias Andree [this message]
     [not found] <20010905170037.A6473@emma1.emma.line.org.suse.lists.linux.kernel>
     [not found] ` <20010905152738.C5912BC06D@spike.porcupine.org.suse.lists.linux.kernel>
     [not found]   ` <20010905182033.D3926@emma1.emma.line.org.suse.lists.linux.kernel>
2001-09-05 19:26     ` Andi Kleen
2001-09-06 13:11       ` Matthias Andree
2001-09-06 13:35       ` Andrey Savochkin
2001-09-06 14:04         ` Wietse Venema
2001-09-06 14:21           ` Matthias Andree
2001-09-06 14:51           ` Alan Cox
2001-09-06 14:17         ` Matthias Andree
2001-09-08 12:42     ` Kai Henningsen
2001-09-09  0:37       ` Matthias Andree
     [not found] <fa.k8o5i6v.4i8gis@ifi.uio.no>
     [not found] ` <fa.fuk70gv.mk6m09@ifi.uio.no>
2001-09-06 21:19   ` Sam Varshavchik
     [not found] <20010905170037.A6473@emma1.emma.line.org>
     [not found] ` <20010905152738.C5912BC06D@spike.porcupine.org>
2001-09-05 16:20   ` Matthias Andree
2001-09-05 18:25     ` Christopher Friesen
2001-09-05 18:34       ` Alan Cox
2001-09-05 21:23         ` Wietse Venema
2001-09-06 18:36           ` Andi Kleen
2001-09-06 18:51             ` Wietse Venema
2001-09-06 19:05               ` Andi Kleen
2001-09-07  9:30               ` Henning P. Schmiedehausen
2001-09-07 11:15                 ` Matthias Andree

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=20010906222228.I13547@emma1.emma.line.org \
    --to=matthias.andree@stud.uni-dortmund.de \
    --cc=ak@muc.de \
    --cc=hadi@cyberus.ca \
    --cc=kuznet@ms2.inr.ac.ru \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@oss.sgi.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).