The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Paul Dickson <dickson@permanentmail.com>
To: Ingo Oeser <ioe-lkml@rameria.de>
Cc: jengelh@linux01.gwdg.de, linux-kernel@vger.kernel.org
Subject: Re: state terminology
Date: Sun, 15 Jan 2006 13:00:24 -0700	[thread overview]
Message-ID: <20060115130024.0db8fb1c.dickson@permanentmail.com> (raw)
In-Reply-To: <200601151058.55369.ioe-lkml@rameria.de>

On Sun, 15 Jan 2006 10:58:48 +0100, Ingo Oeser wrote:

> Hi Jan,
> 
> On Saturday 14 January 2006 22:34, you wrote:
> > Is there a specific term (other than "hang") associated with this 
> > situation? It's not a "dead-lock", because there is no other process 
> > (anymore) which could potentially up the semaphore.
> 
> This is a simple "resource leak" (or "semaphore leak" in this case).
> 
> Explanation follows:
> 
> The resource semaphore is not usable by anyone anymore 
> and is still around.
> 
> Its pretty much the same as a memory leak. There is no one, who
> could free the memory anymore.
> 
> The reasons for the resource not being usable anymore is
> not significant for a resource leak.
> 
> Also insignificant is the fact that the amount of semaphores
> are just limited by available memory. If you repeat starting threads 
> doing the semaphore leak game from your example, you'll run out
> of memory and thus out of semaphores. This is another sign of leakage.
> 
> Do the above explanations sound ok?

But it's the functionality rather than the resource that's being lost.
So I wouldn't consider it to be a leak.

How about "locked-out" or "lock-out"?  It's akin to a locked room, with
the keys left inside.

	-Paul


  reply	other threads:[~2006-01-15 20:00 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-14 21:34 state terminology Jan Engelhardt
2006-01-15  9:58 ` Ingo Oeser
2006-01-15 20:00   ` Paul Dickson [this message]
2006-01-15 20:55     ` Jan Engelhardt

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=20060115130024.0db8fb1c.dickson@permanentmail.com \
    --to=dickson@permanentmail.com \
    --cc=ioe-lkml@rameria.de \
    --cc=jengelh@linux01.gwdg.de \
    --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