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-next>] [day] [month] [year] [list]

Message-Id: <200805151030.18959.rusty@rustcorp.com.au>
Date:	Thu, 15 May 2008 10:30:18 +1000
From:	Rusty Russell <rusty@...tcorp.com.au>
To:	"Matti Linnanvuori" <mattilinn@...il.com>
Cc:	"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 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?

Thanks,
Rusty.
PS. Patch fixed up and applied.
--
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/