From: Peter Zijlstra <peterz@infradead.org>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: Anirban Sinha <ani@anirban.org>, Ingo Molnar <mingo@elte.hu>,
linux-kernel@vger.kernel.org, Darren Hart <dvhltc@us.ibm.com>,
Kaz Kylheku <kaz@zeugmasystems.com>,
Anirban Sinha <asinha@zeugmasystems.com>
Subject: Re: futex question
Date: Mon, 05 Oct 2009 14:18:39 +0200 [thread overview]
Message-ID: <1254745119.26976.43.camel@twins> (raw)
In-Reply-To: <alpine.LFD.2.00.0910051358060.2646@localhost.localdomain>
On Mon, 2009-10-05 at 13:59 +0200, Thomas Gleixner wrote:
> Stared at the same place a minute ago :) But still I wonder if it's a
> good idea to silently release locks and set the state to OWNERDEAD
> instead of hitting the app programmer with a big clue stick in case
> the app holds locks when calling execve().
Agreed, I rather like the feedback. With regular exit like things
there's just not much we can do to avoid the mess, but here we can
actually avoid it, seems a waste not to do so.
next prev parent reply other threads:[~2009-10-05 12:16 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-30 1:10 Anirban Sinha
2009-10-01 9:22 ` Ingo Molnar
2009-10-01 16:54 ` Anirban Sinha
2009-10-01 23:46 ` Anirban Sinha
2009-10-02 23:38 ` Darren Hart
2009-10-03 0:36 ` Anirban Sinha
2009-10-03 4:14 ` Eric Dumazet
2009-10-04 8:44 ` Thomas Gleixner
[not found] ` <DDFD17CC94A9BD49A82147DDF7D545C501F457C5@exchange.ZeugmaSystems.local>
2009-10-04 16:37 ` Anirban Sinha
2009-10-04 16:59 ` Thomas Gleixner
2009-10-05 10:36 ` Peter Zijlstra
2009-10-05 10:56 ` Thomas Gleixner
2009-10-05 11:16 ` Peter Zijlstra
2009-10-05 11:19 ` Ingo Molnar
2009-10-05 11:50 ` Thomas Gleixner
2009-10-05 11:47 ` Thomas Gleixner
2009-10-05 13:11 ` Anirban Sinha
2009-10-05 13:28 ` Thomas Gleixner
2009-10-05 14:03 ` Anirban Sinha
2009-10-05 18:36 ` Anirban Sinha
2009-10-05 11:58 ` Peter Zijlstra
2009-10-05 11:59 ` Thomas Gleixner
2009-10-05 12:18 ` Peter Zijlstra [this message]
2009-10-05 12:24 ` Ingo Molnar
2009-10-05 14:09 ` Darren Hart
2009-10-05 18:11 ` Anirban Sinha
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=1254745119.26976.43.camel@twins \
--to=peterz@infradead.org \
--cc=ani@anirban.org \
--cc=asinha@zeugmasystems.com \
--cc=dvhltc@us.ibm.com \
--cc=kaz@zeugmasystems.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=tglx@linutronix.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
Powered by JetHome