|
|
Message-ID: <20161201191543.GG3124@twins.programming.kicks-ass.net>
Date: Thu, 1 Dec 2016 20:15:43 +0100
From: Peter Zijlstra <peterz@...radead.org>
To: "Reshetova, Elena" <elena.reshetova@...el.com>
Cc: "kernel-hardening@...ts.openwall.com" <kernel-hardening@...ts.openwall.com>,
Greg KH <gregkh@...uxfoundation.org>,
Kees Cook <keescook@...omium.org>,
"will.deacon@....com" <will.deacon@....com>,
Boqun Feng <boqun.feng@...il.com>,
Hans Liljestrand <ishkamiel@...il.com>,
David Windsor <dwindsor@...il.com>, "aik@...abs.ru" <aik@...abs.ru>,
"david@...son.dropbear.id.au" <david@...son.dropbear.id.au>
Subject: Re: Conversion from atomic_t to refcount_t: summary of issues
On Tue, Nov 29, 2016 at 03:35:15PM +0000, Reshetova, Elena wrote:
> but Hans will be finishing processing
> > > The following functions are also needed quite commonly:
> >
> > > refcount_inc_return()
> > > refcount_dec_return()
> >
> > What for? They don't typicaly make sense for refcounting? Other than the
> > trivial pattern of dec_return() == 0, which is already well covered.
Hans, could you point me to a few users of {inc,dec}_return() that I can
audit for (in)sanity?
Powered by blists - more mailing lists
Confused about mailing lists and their use? Read about mailing lists on Wikipedia and check out these guidelines on proper formatting of your messages.