linux-kernel - Re: Subject: [PATCH 2/2] priority System V Semaphores

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: <1324544352.24803.9.camel@twins>
Date:	Thu, 22 Dec 2011 09:59:12 +0100
From:	Peter Zijlstra <peterz@...radead.org>
To:	raz ben yehuda <raziebe@...il.com>
Cc:	Manfred Spraul <manfred@...orfullife.com>,
	linux-rt-users@...r.kernel.org, linux-kernel@...r.kernel.org,
	Lior Brafman <LBrafman@...z.com>,
	Torsten Scherer <TScherer@...z.com>,
	Rasty Slutsker <RSlutsker@...z.com>
Subject: Re: Subject: [PATCH 2/2] priority System V Semaphores

On Wed, 2011-12-21 at 22:48 +0200, raz ben yehuda wrote:
> Vxworks is the use case. And there are plenty of companies with
> vxWorks software and in i believe they will migrate sooner or later to
> PreemptRT.  My current company uses old wrapper software that implements
> vxWorks semaphores as system V semaphores. vxWorks semaphores have a priority
> feature which is widely used.
> I will probably change it some time in the future to posix semaphores , but posix 
> semaphores are implemented in glibc with futexes and atomic ops and i rather 
> mess with kernel and not glibc. funny , but true. glibc is harder. 

Semaphores are a fscking trainwreck for real-time programming. Don't use
them, full stop. If you do, you're doing it wrong, it's really that
simple.

Use PI mutexes, which are already fully supported in glibc, no extra
patching needed.

Full NAK for any and all priority fudging for any semaphore
implementation.
--
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/