linux-kernel - Re: [PATCH v3] refcount: add refcount

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: <CAGXu5jLfDdq1E0vXda4tqrHSqSGhk76Biemh6axaycOB+E-zfQ@mail.gmail.com>
Date:   Thu, 23 Mar 2017 07:06:55 -0700
From:   Kees Cook <keescook@...omium.org>
To:     Ingo Molnar <mingo@...nel.org>
Cc:     David Windsor <dwindsor@...il.com>,
        Peter Zijlstra <peterz@...radead.org>,
        "Reshetova, Elena" <elena.reshetova@...el.com>,
        LKML <linux-kernel@...r.kernel.org>,
        "kernel-hardening@...ts.openwall.com" 
        <kernel-hardening@...ts.openwall.com>
Subject: Re: [PATCH v3] refcount: add refcount_t API kernel-doc comments

On Thu, Mar 23, 2017 at 12:40 AM, Ingo Molnar <mingo@...nel.org> wrote:
>
> * Kees Cook <keescook@...omium.org> wrote:
>
>> On Fri, Mar 10, 2017 at 7:34 AM, David Windsor <dwindsor@...il.com> wrote:
>> > v3: rebase against latest Linus tree; re-add include/linux/refcount.h
>> > missing from v2 series
>> >
>> > Signed-off-by: David Windsor <dwindsor@...il.com>
>>
>> Reviewed-by: Kees Cook <keescook@...omium.org>
>>
>> Ingo, can you pull this into tip? I like having more documentation here. :)
>
> So I hopped into my time machine and applied it to tip:locking/core as of March
> 13th:
>
>   commit bd174169c7a12a37b3b4aa2221f084ade010b182
>   Author:     David Windsor <dwindsor@...il.com>
>   AuthorDate: Fri Mar 10 10:34:12 2017 -0500
>   Commit:     Ingo Molnar <mingo@...nel.org>
>   CommitDate: Mon Mar 13 07:41:08 2017 +0100
>
> You are welcome! ;-)

I love time-travelling maintainers! They are very tolerant of people
who don't double-check -next first. :)

Thanks!

-Kees

-- 
Kees Cook
Pixel Security