Message-ID: <40E1BE7D.7070806@redhat.com>
Date: Tue, 29 Jun 2004 12:09:49 -0700
From: Ulrich Drepper <drepper@redhat.com>
Organization: Red Hat, Inc.
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8a2) Gecko/20040627
MIME-Version: 1.0
To: "David S. Miller" <davem@redhat.com>
CC: linux-kernel@vger.kernel.org
Subject: Re: inconsistency between SIOCGIFCONF and SIOCGIFNAME
References: <40E0EAC1.50101@redhat.com> <20040629012604.20c3ad8b.davem@redhat.com>
In-Reply-To: <20040629012604.20c3ad8b.davem@redhat.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1118
Lines: 27

David S. Miller wrote:

> I enclose a potential implementation for the ipv4 instance.
> Please at least make sure it does what you want.

Seems to work nicely.


> I really really hope there is not some application out there
> that assumes that devices reported by SIOCGIFCONF are all up.
> That works now, and we'd break things by making the suggested
> change.  So this is what I'm most concerned about.

The worst that could happen is that some more interfaces are reported.
Since the information provided by SIOCGIFCONF isn't really enough to do
anything meaningful other calls are needed at which point those
interfaces can be weeded out, if this is wanted.  Also, the address
family reported for those interfaces is AF_UNSPEC which should be a hint
strong enough to recognize them.

-- 
➧ Ulrich Drepper ➧ Red Hat, Inc. ➧ 444 Castro St ➧ Mountain View, CA ❖
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/