linux-kernel - Re: [PATCH] Replace completions with 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]

Date:	Tue, 15 Apr 2008 08:46:56 +0200
From:	Peter Zijlstra <peterz@...radead.org>
To:	Bart Van Assche <bart.vanassche@...il.com>
Cc:	Andi Kleen <andi@...stfloor.org>,
	Roland Dreier <rdreier@...co.com>, Ingo Molnar <mingo@...e.hu>,
	Matthew Wilcox <matthew@....cx>,
	Ingo Oeser <ioe-lkml@...eria.de>,
	Daniel Walker <dwalker@...sta.com>,
	linux-kernel@...r.kernel.org, Linus Torvalds <torvalds@...l.org>
Subject: Re: [PATCH] Replace completions with semaphores

On Tue, 2008-04-15 at 08:18 +0200, Bart Van Assche wrote:
> On Mon, Apr 14, 2008 at 9:16 PM, Andi Kleen <andi@...stfloor.org> wrote:
> >  For me it sounds like you just want to rename semaphores to some other
> >  name that people don't use them for normal locking?
> 
> Would it really be a good idea to give a synchronization concept that
> behaves exactly like a semaphore another name than "semaphore" ? The
> semaphore concept is well known and is taught in every computer
> science course.

Are the ramifications wrt priority inversion taught? Is it made clear
that its hard to validate because there is no clear resource owner?

Afaik, non of these subjects are touched upon in the CS-101 courses and
that is exactly the problem. So you can say they are not well know, they
are just widely misunderstood.

And yes, if there are more hand a very few such users it doesn't make
sense to keep them open coded.

--
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/