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: <CAGXu5j+51gKaeU7jd8=GUO87PfRRGbKwEHhbQDHrc8Ohynwdcw@mail.gmail.com>
Date:   Thu, 7 Dec 2017 09:59:51 -0800
From:   Kees Cook <keescook@...omium.org>
To:     Jonathan Corbet <corbet@....net>
Cc:     Elena Reshetova <elena.reshetova@...el.com>,
        linux-doc@...r.kernel.org, Peter Zijlstra <peterz@...radead.org>,
        LKML <linux-kernel@...r.kernel.org>,
        Dave Chinner <david@...morbit.com>
Subject: Re: [PATCH] docs: refcount_t documentation

On Thu, Dec 7, 2017 at 9:58 AM, Jonathan Corbet <corbet@....net> wrote:
> On Tue,  5 Dec 2017 12:46:35 +0200
> Elena Reshetova <elena.reshetova@...el.com> wrote:
>
>> Some functions from refcount_t API provide different
>> memory ordering guarantees that their atomic counterparts.
>> This adds a document outlining these differences (
>> Documentation/core-api/refcount-vs-atomic.rst) as well as
>> some other minor improvements.
>
> This seems generally good to me.  Did you want me to take it through the
> docs tree (including the refcount.h change) or did you have some other
> path in mind?

FWIW, I had assumed this would go via the docs tree.

-Kees

-- 
Kees Cook
Pixel Security

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ