All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Peter Wächtler" <pwaechtler@loewe-komp.de>
To: Vladimir Zidar <vladimir@mindnever.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Process-Shared Mutex (futex) - What is it good for ?
Date: Tue, 11 Jun 2002 15:19:07 +0200	[thread overview]
Message-ID: <3D05F8CB.7040409@loewe-komp.de> (raw)
In-Reply-To: <1023380463.1751.39.camel@server1> 	<3D00706B.1070906@loewe-komp.de> <1023481074.7204.70.camel@server1> 	<3D0324B1.614BD9D4@loewe-komp.de> <1023723807.1491.56.camel@server1>

Vladimir Zidar wrote:
> On Sun, 2002-06-09 at 11:49, Peter Wächtler wrote:
> 
> 
>>Just for *that*?
>>Do you write programs that reveal from sigsegv with sigsetjmp(3)?
>>
> 
>  No, I do not. But killing the process sounds much like abnormal
> programm termination. Can you feel the word 'abnormal' ? It is opposite
> of normal - be it simple as error condition on file descriptor.
> 

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


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.

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



  reply	other threads:[~2002-06-11 13:17 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 [this message]
2002-06-11 17:18           ` Vladimir Zidar

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=3D05F8CB.7040409@loewe-komp.de \
    --to=pwaechtler@loewe-komp.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=vladimir@mindnever.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.