netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: cl@linux.com
Cc: niv@us.ibm.com, nhorman@tuxdriver.com, netdev@vger.kernel.org,
	vladislav.yasevich@hp.com, dlstevens@us.ibm.com
Subject: Re: PATCH: Multicast: Filter multicast traffic per socket mc_list
Date: Fri, 17 Apr 2009 15:24:12 -0700 (PDT)	[thread overview]
Message-ID: <20090417.152412.96128121.davem@davemloft.net> (raw)
In-Reply-To: <alpine.DEB.1.10.0904171158220.13734@qirst.com>

From: Christoph Lameter <cl@linux.com>
Date: Fri, 17 Apr 2009 12:02:19 -0400 (EDT)

> On Fri, 17 Apr 2009, Nivedita Singhvi wrote:
> 
>> I need the current behaviour to not change, as it would
>> break some people I support.  DaveM is making the right
>> decision here, and I fully support this.
> 
> People or applications? There are applications that only run on Linux and
> fail on other OS? How does this work? Special casing depending on the OS
> running?

Christoph I just want to let you know that I'm totally ignoring
everything further you say on this issue, becuase you're way out of
line and totally ignoring the real issues here.

What's next?  Tomorrow, if you think Linux's open() system call
behavior doesn't suit your needs, I want you to send a sysctl patch to
Al Viro that changes the system wide behavior and we'll see how far
you get with that.

The fact is, you cannot just say "oops we didn't mean to do that" when
something has behaved a certain way, visible to users, for more that
15 years.

And the fact is, WE DID MEAN to do things this way.

As David Stevens explained, the original creator of multicasting, the
original BSD code, and the RFCs, INTENDED this behavior from the very
beginning.

You want to ignore all of this, as if none of it matters and that what
you want to achieve is so much more important.

  parent reply	other threads:[~2009-04-17 22:24 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-16 14:38 PATCH: Multicast: Filter multicast traffic per socket mc_list Christoph Lameter
2009-04-16 15:09 ` David Stevens
2009-04-16 15:36   ` Christoph Lameter
2009-04-16 22:15     ` David Miller
2009-04-16 15:15 ` Neil Horman
2009-04-16 15:36   ` Christoph Lameter
2009-04-16 17:44     ` Neil Horman
2009-04-16 19:12       ` Christoph Lameter
2009-04-16 20:56         ` David Stevens
2009-04-16 21:04           ` Christoph Lameter
2009-04-16 21:54             ` David Stevens
2009-04-16 22:19             ` David Miller
2009-04-16 21:19           ` Vlad Yasevich
2009-04-16 22:20             ` David Miller
2009-04-16 22:22             ` David Stevens
2009-04-16 23:30               ` Stephen Hemminger
2009-04-17  0:01               ` Vlad Yasevich
2009-04-16 22:16         ` David Miller
2009-04-17 13:56           ` Christoph Lameter
2009-04-17 15:37             ` Nivedita Singhvi
2009-04-17 16:02               ` Christoph Lameter
2009-04-17 16:28                 ` Nivedita Singhvi
2009-04-17 22:24                 ` David Miller [this message]
2009-04-20 18:10                   ` Christoph Lameter
2009-04-17 21:31             ` David Stevens
2009-04-20 16:43               ` Christoph Lameter
2009-04-20 18:46                 ` David Stevens
2009-04-16 15:24 ` Vlad Yasevich
2009-04-16 15:39   ` Christoph Lameter

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=20090417.152412.96128121.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=cl@linux.com \
    --cc=dlstevens@us.ibm.com \
    --cc=netdev@vger.kernel.org \
    --cc=nhorman@tuxdriver.com \
    --cc=niv@us.ibm.com \
    --cc=vladislav.yasevich@hp.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).