linux-kernel - Re: [PATCH 1/5] doc/memory-barriers: fix missed renaming: s/lock/acquire

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:	Thu, 10 Mar 2016 23:39:35 +0900
From:	SeongJae Park <sj38.park@...il.com>
To:	David Howells <dhowells@...hat.com>
Cc:	Paul McKenney <paulmck@...ux.vnet.ibm.com>,
	Jonathan Corbet <corbet@....net>,
	Minchan Kim <minchan@...nel.org>,
	linux-doc <linux-doc@...r.kernel.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 1/5] doc/memory-barriers: fix missed renaming: s/lock/acquire

On Thu, Mar 10, 2016 at 6:45 PM, David Howells <dhowells@...hat.com> wrote:
> SeongJae Park <sj38.park@...il.com> wrote:
>
>> >> -     - Locking functions.
>> >> +     - Acquiring functions.
>> ...
>> > It's specifically talking about locking functions that the kernel provides -
>> > or are we calling the spin acquires and R/W spin acquires now?  "Locking" is
>> > the key that people referring to the document are going to use.
>>
>> AFAIU, the next line of the quoted text says the section is talking about
>> variants on "ACQUIRE" operations and "RELEASE" operations for each locking
>> constructs.
>
> Whilst that's true, most people think of them as locks.  You could change the
> name of the section to:
>
>         Locking/Acquiring functions
>
> or:
>
>         Lock acquisition functions

Thank you for your suggestion, David.  I will send new patchset ASAP.

Thanks,
SeongJae Park

>
> perhaps.
>
> David