linux-kernel - Re: [patch] doc: add a chapter about trylock functions [Bug 9011]

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:	Fri, 16 May 2008 14:21:25 +0200
From:	Peter Zijlstra <peterz@...radead.org>
To:	Rusty Russell <rusty@...tcorp.com.au>
Cc:	Matti Linnanvuori <mattilinn@...il.com>,
	Randy Dunlap <randy.dunlap@...cle.com>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Ingo Molnar <mingo@...e.hu>, linux-kernel@...r.kernel.org
Subject: Re: [patch] doc: add a chapter about trylock functions [Bug 9011]

On Thu, 2008-05-15 at 10:30 +1000, Rusty Russell wrote:
> On Wednesday 14 May 2008 01:31:47 Matti Linnanvuori wrote:
> > +    <function>mutex_trylock()</function> does not suspend your task
> > +    but returns non-zero if it could lock the mutex on the first try
> > +    or 0 if not. This function cannot be safely used in hardware or
> > +    software interrupt contexts despite not sleeping.
> 
> I know this is what the documentation says, but I can't see why.  Ingo?

because who would then own the lock?

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/