From: "David S. Miller" <davem@redhat.com>
To: kuznet@ms2.inr.ac.ru
Cc: jmorris@redhat.com, hidden@balabit.hu, netdev@oss.sgi.com,
linux-net@vger.rutgers.edu
Subject: Re: Fw: Re: [PATCH] ipv4 tcp autobind problem
Date: Tue, 30 Sep 2003 05:37:57 -0700 [thread overview]
Message-ID: <20030930053757.36965bf3.davem@redhat.com> (raw)
In-Reply-To: <200309301237.QAA01426@yakov.inr.ac.ru>
On Tue, 30 Sep 2003 16:37:48 +0400 (MSD)
kuznet@ms2.inr.ac.ru wrote:
> From this mail I still do not see why autobinding of void socket is so
> bad thing, that it requires marginal fixing at the place which is already
> marginal. What is the real problem?
I think it is some detail about their transparent proxy kernel
hacks, remember that awful stuff? :)
next prev parent reply other threads:[~2003-09-30 12:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20030930024320.5aca8ddc.davem@redhat.com>
2003-09-30 12:37 ` Fw: Re: [PATCH] ipv4 tcp autobind problem kuznet
2003-09-30 12:37 ` David S. Miller [this message]
2003-09-30 14:19 ` Kovacs Krisztian
2003-10-07 11:56 ` kuznet
2003-10-07 12:35 ` Kovacs Krisztian
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=20030930053757.36965bf3.davem@redhat.com \
--to=davem@redhat.com \
--cc=hidden@balabit.hu \
--cc=jmorris@redhat.com \
--cc=kuznet@ms2.inr.ac.ru \
--cc=linux-net@vger.rutgers.edu \
--cc=netdev@oss.sgi.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).