linux-kernel - Re: [PATCH] Documentation of current lglocks implementation

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

Message-ID: <20141208095637.GB2821@hudson.localdomain>
Date:	Mon, 8 Dec 2014 01:56:37 -0800
From:	Jeremiah Mahler <jmmahler@...il.com>
To:	Nicholas Mc Guire <der.herr@...r.at>
Cc:	linux-doc@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] Documentation of current lglocks implementation

Nicholas,

On Mon, Dec 08, 2014 at 09:33:26AM +0100, Nicholas Mc Guire wrote:
> 
> Documentation of current lglocks implementation
> 
> local/global locks are currently not documented anywhere other
> than in an somewhat out-of-date LWN article - this is an attempt
[...]
> +Implementation:
> +---------------
> +
> +The initial lglock implementation from Nick Piggin used some complex
> +macros to generate the lglock/brlock in lglock.h - they were later
> +turned into a set of functions by Andi Kleen [7]. The change to functions
> +was motivated by the presence of multiple lock users and also by them
> +being easier to maintain than the generating macros. This change to
> +functions is also the basis to eliminated the restriction of not
> +being initializeable in kernel modules (the remaining problem is that
         ^^^^^^^^^^^^^^
		 initializable

> +locks are not explicitly initialized - see lockdep-design.txt)
> +
> +Declaration and initialization:
> +-------------------------------
> +
> +  #include <linux/lglock.h>
[...]

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