From: David Miller <davem@davemloft.net>
To: jharan@Brocade.COM
Cc: netdev@vger.kernel.org
Subject: Re: NETLINK sockets dont honor SO_RCVLOWAT?
Date: Wed, 18 Nov 2009 11:09:18 -0800 (PST) [thread overview]
Message-ID: <20091118.110918.154510772.davem@davemloft.net> (raw)
In-Reply-To: <D67825C5985D0647BE40A5F5B0B70D1106E9C5690C@HQ-EXCH-7.corp.brocade.com>
From: Jeff Haran <jharan@Brocade.COM>
Date: Wed, 18 Nov 2009 11:00:35 -0800
> If the open source community doesn't want a fix for something that
> is obviously broken, that's fine.
It is a bug in your opinion, and adding a check for these cases
doesn't necessarily make the kernel any better.
You can even check BSD, it behaves just like we do for several socket
options (they are just pieces of state stored in the socket, having
protocol specific checks and/or callbacks for every single socket
option would be just a lot of useless bloat).
And when all else fails BSD's behavior is what we use to determine
what is reasonable.
prev parent reply other threads:[~2009-11-18 19:09 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-18 1:54 NETLINK sockets dont honor SO_RCVLOWAT? Jeff Haran
2009-11-18 7:17 ` David Miller
2009-11-18 18:22 ` Jeff Haran
2009-11-18 18:24 ` David Miller
2009-11-18 18:41 ` Jeff Haran
2009-11-18 18:44 ` David Miller
2009-11-18 19:00 ` Jeff Haran
2009-11-18 19:09 ` David Miller [this message]
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=20091118.110918.154510772.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=jharan@Brocade.COM \
--cc=netdev@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 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).