From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <linux-kernel-owner@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
        id S1754791AbdA0J6m (ORCPT <rfc822;w@1wt.eu>);
        Fri, 27 Jan 2017 04:58:42 -0500
Received: from bombadil.infradead.org ([65.50.211.133]:33050 "EHLO
        bombadil.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
        with ESMTP id S932357AbdA0J6L (ORCPT
        <rfc822;linux-kernel@vger.kernel.org>);
        Fri, 27 Jan 2017 04:58:11 -0500
Date: Fri, 27 Jan 2017 10:58:01 +0100
From: Peter Zijlstra <peterz@infradead.org>
To: Kees Cook <keescook@chromium.org>
Cc: Greg KH <gregkh@linuxfoundation.org>,
        Will Deacon <will.deacon@arm.com>,
        "Reshetova, Elena" <elena.reshetova@intel.com>,
        Arnd Bergmann <arnd@arndb.de>, Thomas Gleixner <tglx@linutronix.de>,
        Ingo Molnar <mingo@kernel.org>, "H. Peter Anvin" <hpa@zytor.com>,
        David Windsor <dave@progbits.org>, LKML <linux-kernel@vger.kernel.org>,
        Hans Liljestrand <ishkamiel@gmail.com>
Subject: Re: [RFC][PATCH 7/7] kref: Implement using refcount_t
Message-ID: <20170127095801.GG6515@twins.programming.kicks-ass.net>
References: <20161114173946.501528675@infradead.org>
 <20161114174446.832175072@infradead.org>
 <CAGXu5jKHZ3O5fy7iBSr3=wci7Np0FCTFtAEFKE=NQWCG1bQ7Og@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <CAGXu5jKHZ3O5fy7iBSr3=wci7Np0FCTFtAEFKE=NQWCG1bQ7Og@mail.gmail.com>
User-Agent: Mutt/1.5.23.1 (2014-03-12)
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org

On Thu, Jan 26, 2017 at 03:14:41PM -0800, Kees Cook wrote:
> On Mon, Nov 14, 2016 at 9:39 AM, Peter Zijlstra <peterz@infradead.org> wrote:
> > Provide refcount_t, an atomic_t like primitive built just for
> > refcounting.
> >
> > It provides overflow and underflow checks as well as saturation
> > semantics such that when it overflows, we'll never attempt to free it
> > again, ever.
> >
> > Signed-off-by: Peter Zijlstra (Intel) <peterz@infradead.org>
> 
> Hi!
> 
> I see the other 6 patches from this series are in -next, but the
> refcount_t implementation is still missing. What's needed to land this
> in -next? It's blocking sending the atomic_t -> refcount_t patches,
> which will likely all go through various maintainers, so we need to
> have refcount_t first. :)

Nothing much, except lack of time. I spend the last several days hunting
bugs, that trumps new features on my todo list.