From: Andrew Lunn <andrew@lunn.ch>
To: Tad <ecos_removethispart@ds3switch.com>
Cc: ecos-discuss@sources.redhat.com
Subject: Re: [ECOS] accept() FreeBSD hangs when out of resources
Date: Mon, 11 Jun 2007 22:14:00 -0000 [thread overview]
Message-ID: <20070611215236.GF26816@lunn.ch> (raw)
In-Reply-To: <466DC965.5010803@ds3switch.com>
On Mon, Jun 11, 2007 at 02:15:01PM -0800, Tad wrote:
> accept() won't return and won't timeout (>12hrs) when listen() indicates
> a new connection, if out of sockets/file-descriptors and all TCP
> connections are in ESTABLISHED state.
Where exactly is it blocked. Please could you provide a call stack.
The new fd and socket descriptor appears to be allocated in the fileio
code before the network stack accept function is called. And i don't
see how they can block when out of resources.
> My other FreeBSD bug posts to bugzilla seem to be ignored, so I won't
> bother sending this one there.
The often are, since most of us don't automatically get notification
of there creation and I in particular only poll it once a month or
less.
Andrew
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
prev parent reply other threads:[~2007-06-11 21:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-11 21:52 Tad
2007-06-11 22:14 ` Andrew Lunn [this message]
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=20070611215236.GF26816@lunn.ch \
--to=andrew@lunn.ch \
--cc=ecos-discuss@sources.redhat.com \
--cc=ecos_removethispart@ds3switch.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 read-only IMAP folder(s) and NNTP newsgroup(s).