linux-kernel - Re: [PATCH 2/3] locking: ww_mutex: Allow to use rt

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: <54F99A38.1070806@linutronix.de>
Date:	Fri, 06 Mar 2015 13:14:48 +0100
From:	Sebastian Andrzej Siewior <bigeasy@...utronix.de>
To:	Maarten Lankhorst <maarten.lankhorst@...onical.com>,
	Mike Galbraith <umgwanakikbuti@...il.com>
CC:	linux-kernel@...r.kernel.org,
	Peter Zijlstra <peterz@...radead.org>,
	Ingo Molnar <mingo@...hat.com>
Subject: Re: [PATCH 2/3] locking: ww_mutex: Allow to use rt_mutex instead
 of mutex for the baselock

On 03/02/2015 09:46 AM, Maarten Lankhorst wrote:
> Hey,
> 
> Op 02-03-15 om 04:20 schreef Mike Galbraith:
>> On Fri, 2015-02-27 at 17:57 +0100, Sebastian Andrzej Siewior wrote:
>>> This patch makes it possible to replace the base mutex by a rt_mutex. In
>>> general one would not do this.
>> I would argue that the thing should be born as a full fledged primitive,
>> not a config option, as an rt_ww_mutex is the ww extension of rt_mutex.
>> We have to do the global substitution in -rt, but why should it not
>> exist in its own right in mainline? 
> Well I haven't seen any users that specifically need a rt_ww_mutex, but flipping the switch on ww_mutex could be useful for testing. :)

Okay so what I the point made here? It is only about the config option,
right? What are the preferences here:
[ ] yes, the way it is now
[ ] yes, but somewhere else, please enter where you would like to see it

[ ] yes, but keep it hidden (not selectable)

[ ] what?

> ~Maarten


Sebastian

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