mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Matthias Andree <matthias.andree@stud.uni-dortmund.de>
To: Andi Kleen <ak@muc.de>
Cc: kuznet@ms2.inr.ac.ru, tao@acc.umu.se, matthias.andree@gmx.de,
	alan@lxorguk.ukuu.org.uk, wietse@porcupine.org,
	linux-kernel@vger.kernel.org, linux-net@vger.kernel.org,
	netdev@oss.sgi.com
Subject: Re: [PATCH] ioctl SIOCGIFNETMASK: ip alias bug 2.4.9 and 2.2.19
Date: Mon, 10 Sep 2001 23:19:11 +0200	[thread overview]
Message-ID: <20010910231911.I30149@emma1.emma.line.org> (raw)
In-Reply-To: <20010910100537.W26627@khan.acc.umu.se> <200109101936.XAA00707@ms2.inr.ac.ru> <20010910224002.31693@colin.muc.de>
In-Reply-To: <20010910224002.31693@colin.muc.de>

Andi Kleen schrieb am Montag, den 10. September 2001:

> > So that applications will have to worry about compatibility with older
> > kernels in any case.
> 
> Just hope then that no ifconfig or other binary has a two on the stack
> when calling this.

Thanks for asking, however, nothing bad will happen if there are no
4.4BSD-style aliases. If there are, you have no business using ifconfig
anyways, and ifconfig certainly has not configured the aliases (it
overwrites the primary address unless you use a separate name such as
eth0:0).

Actually, in net-tools-1.56, ifconfig does write AF_INET onto its ifr
(it gets shot otherwise), without clearing the address field (which
contains the txqueuelen result). However, the worst thing that can
happen is that ifconfig displays one of the aliases - but the alias
would match the txqueuelen then. How many people have 0.0.0.* or *.0.0.0
addresses configured as alias? Not too many. None, to be precise.

It will not bite portable applications either since those init their
address properly.

-- 
Matthias Andree

  reply	other threads:[~2001-09-11 10:41 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20010906155920.B29583@maggie.dt.e-technik.uni-dortmund.de>
     [not found] ` <200109061554.TAA11031@ms2.inr.ac.ru>
2001-09-06 17:48   ` Matthias Andree
2001-09-06 18:06     ` kuznet
2001-09-06 18:18       ` Wietse Venema
2001-09-06 18:38         ` kuznet
2001-09-06 19:45         ` Alan Cox
2001-09-06 19:59           ` Wietse Venema
2001-09-06 20:20             ` jamal
2001-09-06 20:41               ` Wietse Venema
2001-09-06 20:44                 ` jamal
2001-09-06 21:20                   ` Matthias Andree
2001-09-07  6:11                     ` Patrick Schaaf
2001-09-07  9:24                     ` Henning P. Schmiedehausen
2001-09-07 11:13                       ` Matthias Andree
2001-09-08 13:25                     ` Kai Henningsen
2001-09-06 20:22             ` Alan Cox
2001-09-06 20:38               ` Wietse Venema
2001-09-10 16:11             ` Dennis
2001-09-06 20:13           ` Matthias Andree
2001-09-10  8:05             ` David Weinehall
2001-09-10 12:26               ` Wietse Venema
2001-09-10 12:53                 ` David Weinehall
2001-09-10 13:52                   ` Wietse Venema
2001-09-10 15:18                   ` Matthias Andree
2001-09-10 15:12               ` Matthias Andree
2001-09-10 19:36               ` kuznet
2001-09-10 20:14                 ` Matthias Andree
2001-09-11 15:22                   ` kuznet
2001-09-11 16:39                     ` Matthias Andree
2001-09-10 20:40                 ` Andi Kleen
2001-09-10 21:19                   ` Matthias Andree [this message]
2001-09-11 11:26                   ` 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=20010910231911.I30149@emma1.emma.line.org \
    --to=matthias.andree@stud.uni-dortmund.de \
    --cc=ak@muc.de \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=kuznet@ms2.inr.ac.ru \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-net@vger.kernel.org \
    --cc=matthias.andree@gmx.de \
    --cc=netdev@oss.sgi.com \
    --cc=tao@acc.umu.se \
    --cc=wietse@porcupine.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

all inboxes | Powered by JetHome®