All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Zijlstra <peterz@infradead.org>
To: Oleg Drokin <green@linuxhacker.ru>
Cc: Mailing List <linux-kernel@vger.kernel.org>,
	mingo@redhat.com, arjan@linux.intel.com,
	"J . Bruce Fields" <bfields@fieldses.org>,
	Jeff Layton <jlayton@poochiereds.net>
Subject: Re: initialize a mutex into locked state?
Date: Fri, 17 Jun 2016 10:25:59 +0200	[thread overview]
Message-ID: <20160617082559.GD30935@twins.programming.kicks-ass.net> (raw)
In-Reply-To: <55315ADD-4AE1-4EA4-8291-1B07F659BD99@linuxhacker.ru>

On Wed, Jun 15, 2016 at 02:23:35PM -0400, Oleg Drokin wrote:
> Hello!
> 
>   To my surprise I found out that it's not possible to initialise a mutex into
>   a locked state.
>   I discussed it with Arjan and apparently there's no fundamental reason
>   not to allow this.

There is. A mutex _must_ have an owner. If you can initialize it in
locked state, you could do so statically, ie. outside of the context of
a task.

  reply	other threads:[~2016-06-17  8:26 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-15 18:23 initialize a mutex into locked state? Oleg Drokin
2016-06-17  8:25 ` Peter Zijlstra [this message]
2016-06-17 14:14   ` Oleg Drokin
2016-06-17 14:19     ` Peter Zijlstra
2016-06-17 14:24       ` Oleg Drokin
2016-06-17 14:32         ` Peter Zijlstra
2016-06-17 14:40           ` Oleg Drokin
2016-06-17 14:42             ` Jeff Layton
2016-06-17 14:54               ` Oleg Drokin
2016-06-17 14:59                 ` Arjan van de Ven
2016-06-17 14:59             ` Peter Zijlstra
     [not found]         ` <CAC0gvwFhyahkP9M7Ktfd0GOv8CJbkeVegSfc57XpEUk8qAGA1w@mail.gmail.com>
2016-06-17 14:46           ` Oleg Drokin

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=20160617082559.GD30935@twins.programming.kicks-ass.net \
    --to=peterz@infradead.org \
    --cc=arjan@linux.intel.com \
    --cc=bfields@fieldses.org \
    --cc=green@linuxhacker.ru \
    --cc=jlayton@poochiereds.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.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 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.