From: "David S. Miller" <davem@redhat.com>
To: Kovacs Krisztian <hidden@balabit.hu>
Cc: netdev@oss.sgi.com, linux-net@vger.kernel.org
Subject: Re: [PATCH] ipv4 tcp autobind problem
Date: Mon, 29 Sep 2003 22:22:09 -0700 [thread overview]
Message-ID: <20030929222209.4d02c542.davem@redhat.com> (raw)
In-Reply-To: <3F782E1F.4030500@balabit.hu>
Once connect() has been called on a socket, you may not ever again
perform any action that would try to connect that socket.
Said another way, a socket that has failed to connect() is a socket
that you may not use in any usable way ever again except to close
that file descriptor.
next prev parent reply other threads:[~2003-09-30 5:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-29 13:05 [PATCH] ipv4 tcp autobind problem Kovacs Krisztian
2003-09-30 5:22 ` David S. Miller [this message]
2003-09-30 7:14 ` Kovacs Krisztian
-- strict thread matches above, loose matches on Subject: below --
2003-10-07 11:56 Fw: " 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=20030929222209.4d02c542.davem@redhat.com \
--to=davem@redhat.com \
--cc=hidden@balabit.hu \
--cc=linux-net@vger.kernel.org \
--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).