All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ulrich Drepper <drepper@redhat.com>
To: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: inconsistency between SIOCGIFCONF and SIOCGIFNAME
Date: Mon, 28 Jun 2004 21:06:25 -0700	[thread overview]
Message-ID: <40E0EAC1.50101@redhat.com> (raw)

POSIX does not specify the if_indextoname and if_nameindex functions,
they are only vaguely specified in an RFC.  So there is some room for
interpretation but still I think it is an issue.

If SIOCGIFCONF to query the system's interfaces only active interfaces
are returned.  But SIOCGIFNAME (and SIOCGIFINDEX) allow querying
interfaces which are down and not fully initialized.

RFC 3493 says if_nameindex should return *all* interfaces.  This means
that neither if_indextoname or if_nametoindex (defined in the same rfc)
should define more interfaces.


With the current kernels all I could do is to make if_indextoname and
if_nametoindex slower by always calling if_nameindex implicitly to see
whether the interface is defined at all.  It would be much better if the
kernel could do the right thing.  I.e., do one of the following:

~ if the SIOCGIFCONF, return all interfaces SIOCGIFNAME also knows
  about.

~ do not allow SIOCGIFNAME and SIOCGIFINDEX) to return values if
  SIOCGIFCONF, would not return any.

-- 
➧ Ulrich Drepper ➧ Red Hat, Inc. ➧ 444 Castro St ➧ Mountain View, CA ❖

             reply	other threads:[~2004-06-29  4:09 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-29  4:06 Ulrich Drepper [this message]
2004-06-29  8:26 ` inconsistency between SIOCGIFCONF and SIOCGIFNAME David S. Miller
2004-06-29 16:22   ` Ulrich Drepper
2004-06-29 19:09   ` Ulrich Drepper
2004-06-29 21:19     ` David S. Miller
2004-06-30  4:45       ` Ulrich Drepper
2004-06-30  5:10         ` YOSHIFUJI Hideaki / 吉藤英明
2004-06-30  5:13         ` David S. Miller
2004-06-30  7:51           ` Ulrich Drepper
2004-06-30 19:59             ` David S. Miller
2004-06-29 16:32 ` Stephen Hemminger
2004-06-29 19:11   ` Ulrich Drepper

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=40E0EAC1.50101@redhat.com \
    --to=drepper@redhat.com \
    --cc=linux-kernel@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.