Date: Wed, 13 Feb 2002 03:43:24 -0800 (PST)
Message-Id: <20020213.034324.23011197.davem@redhat.com>
To: jgarzik@mandrakesoft.com
Cc: ak@suse.de, linux-net@vger.kernel.org, netdev@oss.sgi.com,
   kuznet@ms2.inr.ac.ru
Subject: Re: IFF_PROMISC bug?
From: "David S. Miller" <davem@redhat.com>
In-Reply-To: <3C6A2789.5DCC1C8F@mandrakesoft.com>
References: <3C6A1EF5.1BF97B99@mandrakesoft.com>
	<20020213.001736.03366378.davem@redhat.com>
	<3C6A2789.5DCC1C8F@mandrakesoft.com>
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-netdev@oss.sgi.com
Precedence: bulk
Content-Length: 862
Lines: 20

   From: Jeff Garzik <jgarzik@mandrakesoft.com>
   Date: Wed, 13 Feb 2002 03:44:57 -0500

   [sigh, I meant to have said that we can support IFF_PROMISC for
   SIOCGIFFLAGS -only-, until the end of time.  I agree with you that
   SIOCSIFFLAGS+IFF_PROMISC clearly is unsupportable.]
   
Then you will break more than what you claim is broken right now.

At least the current code RESPECTS setting IFF_PROMISC if an app uses
SIOCSIFFLAGS to do it, your version would not.

I think you'll be breaking more apps that way, in fact right off the
bat your version will break all current NMAP binaries out there.
That's just the first thing I checked, there are surely several other
examples.

The more and more I look at this situation, the more and more I
respect Alexey's decision to implement things how they are now.
It is the the only reasonable choice, really...