From: Andi Kleen <ak@suse.de>
To: <eg_nth@sinocdn.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: CLOSE_WAIT bug?
Date: 13 Jun 2001 10:55:47 +0200 [thread overview]
Message-ID: <oupwv6glpws.fsf@pigdrop.muc.suse.de> (raw)
In-Reply-To: <Pine.LNX.4.21.0106130037330.10007-200000@sinocdn.com.suse.lists.linux.kernel>
In-Reply-To: <eg_nth@sinocdn.com>'s message of "12 Jun 2001 19:26:27 +0200"
<eg_nth@sinocdn.com> writes:
> Hi all,
>
> I suppect that there is bug in both kernel 2.2.19 and 2.4.5.
> The situation is as follow.
>
> One server socket created and listening, blocking on select(),
> once a client connect to that port, there is another thread in server
> side issues a close() to the new connection.
> After the client close the connection. The connection in server side will
> stuck on CLOSE_WAIT forever until the program being killed.
It is a known problem that unfortunately cannot be easily fixed with the current VFS.
select has a reference to the file handle and it keeps it open until the select ends.
Do a shutdown() in the thread before the close, then the select should wake up.
-Andi
next parent reply other threads:[~2001-06-13 8:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.4.21.0106130037330.10007-200000@sinocdn.com.suse.lists.linux.kernel>
2001-06-13 8:55 ` Andi Kleen [this message]
[not found] <3CA82F7F.312547B8@globalsources.com.suse.lists.linux.kernel>
2002-04-01 17:05 ` CLOSE_WAIT bug? Andi Kleen
2002-04-01 9:59 Beng Asuncion
-- strict thread matches above, loose matches on Subject: below --
2001-06-12 17:30 eg_nth
2001-06-13 2:07 ` David Schwartz
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=oupwv6glpws.fsf@pigdrop.muc.suse.de \
--to=ak@suse.de \
--cc=eg_nth@sinocdn.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.