public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Vladimir Zidar <vladimir@mindnever.org>
To: "Peter Wächtler" <pwaechtler@loewe-komp.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Process-Shared Mutex (futex) - What is it good for ?
Date: 11 Jun 2002 19:18:39 +0200	[thread overview]
Message-ID: <1023815929.1388.93.camel@server1> (raw)
In-Reply-To: <3D05F8CB.7040409@loewe-komp.de>

On Tue, 2002-06-11 at 15:19, Peter Wächtler wrote:

> 
> A-prog:               B-prog:
> 
> gets write lock
> write some data
>                         block on read lock
> write some data
> crashes
>                         wants an error indication to repair data magically

 B-Prog unblocks, but gets -1, with errno=EPIPE.

> 
> 
> So a crashing A-prog is OK for you, but B should get an indication.
> Could catch a signal (SIGLOST?) returning -1 with errno=LOCKBROKEN
> That would be possible with futex.

 Nice if that *would* be possible. But that IS how nutexes are working
already.

> That is a case for writing data to a file - what about linked lists
> in memory?

 Exactly the same. Nutexes are not related to files in any way (other
than /dev/nutex descriptor, but that's completly different thing).


-- 
Bye,

 and have a very nice day !




      reply	other threads:[~2002-06-11 17:18 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-06-06 16:21 Process-Shared Mutex (futex) - What is it good for ? Vladimir Zidar
2002-06-07  8:35 ` Peter Wächtler
2002-06-07 20:17   ` Vladimir Zidar
2002-06-09  9:49     ` Peter Wächtler
2002-06-10 15:43       ` Vladimir Zidar
2002-06-11 13:19         ` Peter Wächtler
2002-06-11 17:18           ` Vladimir Zidar [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=1023815929.1388.93.camel@server1 \
    --to=vladimir@mindnever.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pwaechtler@loewe-komp.de \
    /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