From: kuznet@ms2.inr.ac.ru
To: dyp@perchine.COM (Denis Perchine)
Cc: linux-kernel@vger.kernel.org
Subject: Re: Bad behavior of recv on already closed sockets.
Date: Mon, 11 Dec 2000 22:35:21 +0300 (MSK) [thread overview]
Message-ID: <200012111935.WAA11862@ms2.inr.ac.ru> (raw)
In-Reply-To: <0012111103060F.18833@dyp.perchine.com> from "Denis Perchine" at Dec 11, 0 08:15:00 am
Hello!
> Looks like it tries to read on socket which is already closed from other
> side. And it seems like recv did not return in this case. Is this OK, or
> kernel bug?
This smells like an unknown bug in kernel.
It is unknown, hence there is no workaround (but upgrading to 2.4).
It would be better to understand the issue f.e. trying to restore
the history of this descriptor.
> On the other side I see entries like this:
> httpd 4260 root 4u IPv4 12173018 TCP
> 127.0.0.1:3994->127.0.0.1:5432 (CLOSE_WAIT)
>
> And again. There is no any corresponding postmaster process. Does anyone has
> such expirience before? And what can be the reason of such strange things.
And this is bug in the application, which forgot to close file.
Descriptor leakage in httpd or it is blocked at some another job.
But remembering about the first case, I am not so sure.
What does httpd make this time?
Alexey
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2000-12-11 20:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-12-11 5:03 Denis Perchine
2000-12-11 19:35 ` kuznet [this message]
2000-12-12 12:38 ` Denis Perchine
2000-12-12 19:53 ` kuznet
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=200012111935.WAA11862@ms2.inr.ac.ru \
--to=kuznet@ms2.inr.ac.ru \
--cc=dyp@perchine.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 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®