On Wednesday 14 May 2008 01:31:47 Matti Linnanvuori wrote:
quoted text
> +    <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.
--
unsubscribe notice
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/