From: "David S. Miller" <davem@redhat.com>
To: Andrew Morton <akpm@digeo.com>
Cc: jjs <jjs@tmsusa.com>,
linux-kernel@vger.kernel.org,
James Morris <jmorris@intercode.com.au>
Subject: Re: named vs 2.5.64-mm5
Date: 12 Mar 2003 13:16:53 -0800 [thread overview]
Message-ID: <1047503813.17931.2.camel@rth.ninka.net> (raw)
In-Reply-To: <20030312113126.703de259.akpm@digeo.com>
On Wed, 2003-03-12 at 11:31, Andrew Morton wrote:
> The changelog has:
>
> # --------------------------------------------
> # 03/03/08 jmorris@intercode.com.au 1.1083
> # [NET]: Nuke SO_BSDCOMPAT.
> # --------------------------------------------
>
> Maybe James can tell us what is going on here.
>
> We should at least place a cap on the number of times that message
> is printed.
Feel free to send a patch for that.
SO_BSDCOMPAT has had ZERO side effects since 2.0.x, and it's been
thus scheduled to be removed for years. It was merely a binary
state passed in and out of the kernel to the user and had no effect
on socket behavior at all.
Any application still referencing this ancient thing either expects
some kind of different behavior from setting SO_BSDCOMPAT non-zero,
or really doesn't rely on anything at all.
Since SO_BSDCOMPAT has had zero side effects for 5 or so years, this
means that the safe change is to remove all references to SO_BSDCOMPAT
that exist in any application.
next prev parent reply other threads:[~2003-03-12 21:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-12 18:29 jjs
2003-03-12 19:31 ` Andrew Morton
2003-03-12 21:16 ` David S. Miller [this message]
2003-03-12 22:28 ` jjs
2003-03-12 22:29 ` David S. Miller
2003-03-12 22:31 ` jjs
2003-03-12 19:19 Felipe Alfaro Solana
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=1047503813.17931.2.camel@rth.ninka.net \
--to=davem@redhat.com \
--cc=akpm@digeo.com \
--cc=jjs@tmsusa.com \
--cc=jmorris@intercode.com.au \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®