linux-kernel - Re: [RFC 0/8] Move locking primitives into kernel/locking/

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, 5 Nov 2013 14:26:09 +0100
From:	Ingo Molnar <mingo@...nel.org>
To:	Steven Rostedt <rostedt@...dmis.org>
Cc:	Peter Zijlstra <peterz@...radead.org>,
	torvalds@...ux-foundation.org, akpm@...ux-foundation.org,
	paulmck@...ux.vnet.ibm.com, oleg@...hat.com, dhowells@...hat.com,
	willy@...ux.intel.com, tglx@...utronix.de, airlied@...il.com,
	maarten.lankhorst@...onical.com, walken@...gle.com,
	linux-kernel@...r.kernel.org
Subject: Re: [RFC 0/8] Move locking primitives into kernel/locking/


* Steven Rostedt <rostedt@...dmis.org> wrote:

> On Tue, 05 Nov 2013 13:10:44 +0100
> Peter Zijlstra <peterz@...radead.org> wrote:
> 
> > Hi all,
> > 
> > During Kernel Summit Dave mentioned that there wasn't a clear maintainer for
> > locking bits.
> > 
> > To remedy this Ingo suggested gathering all the various locking primitives and
> > lockdep into a single place: kernel/locking/.
> > 
> > I would further like to propose a MAINTAINERS entry like:
> > 
> > LOCKING
> > M:      Ingo Molnar <mingo@...hat.com>
> > M:      Peter Zijlstra <peterz@...radead.org>
> > M:	Oleg Nesterov <oleg@...hat.com>
> > M:	"Paul E. McKenney" <paulmck@...ux.vnet.ibm.com>
> > M:	Linus Torvalds <torvalds@...ux-foundation.org>
> > T:      git git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git locking/core
> > S:      Maintained
> > F:      kernel/locking/
> 
> I wonder if it should be called kernel/locks, as that's less to type,
> smaller path names, and tastes good on bagels.

The subsystem and topic is generally called 'kernel locking' though, and 
that's what the tree branches have been called for the past couple of 
years as well.

Also, 'kernel lock' brings me back memories of the 'big kernel lock' - 
while 'kernel locks' brings verb/noun ambiguity and visuals of
'kernel locks up'.

As for typing legth: kernel/lo<Tab> autocompletion is your friend! :-)

All in one, I think kernel/locking/ is a better name.

Thanks,

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