linux-kernel - Re: Use of mutex in interrupt context flawed/impossible, need advice.

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

Message-ID: <c384c5ea0711220819j2fa19430sb54139191d181c3b@mail.gmail.com>
Date:	Thu, 22 Nov 2007 17:19:44 +0100
From:	"Leon Woestenberg" <leon.woestenberg@...il.com>
To:	"Oliver Neukum" <oliver@...kum.org>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: Use of mutex in interrupt context flawed/impossible, need advice.

Hello,

On Nov 22, 2007 5:11 PM, Oliver Neukum <oliver@...kum.org> wrote:
> Am Donnerstag 22 November 2007 schrieb Leon Woestenberg:
> > I would like to know why this is not so, and if someone has a cleaner
> > proposal than the "try spinlock" approach?
>
> Keep the semaphore.
>
I forgot to mention that I would like to be prepared for, and use the
-rt patch soon. I understand (maybe wrongly?) that semaphores are not
real-time pre-emptible, mutexes and spinlocks are.

Regards,
-- 
Leon
-
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/