[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1479316156.21171.30.camel@redhat.com>
Date: Wed, 16 Nov 2016 12:09:16 -0500
From: Rik van Riel <riel@...hat.com>
To: kernel-hardening@...ts.openwall.com
Cc: Peter Zijlstra <peterz@...radead.org>, Will Deacon
<will.deacon@....com>,
Greg KH <gregkh@...uxfoundation.org>,
David Windsor
<dave@...gbits.org>,
Elena Reshetova <elena.reshetova@...el.com>,
Arnd
Bergmann <arnd@...db.de>, Thomas Gleixner <tglx@...utronix.de>,
Ingo Molnar
<mingo@...hat.com>,
"H. Peter Anvin" <h.peter.anvin@...el.com>
Subject: Re: Re: [RFC v4 PATCH 00/13] HARDENED_ATOMIC
On Tue, 2016-11-15 at 09:23 -0800, Kees Cook wrote:
> On Tue, Nov 15, 2016 at 8:50 AM, Rik van Riel <riel@...hat.com>
> wrote:
> >
> > On Mon, 2016-11-14 at 12:31 -0800, Kees Cook wrote:
> > >
> > > Keeping the implementation details of refcount_t and stats_t
> > > opaque
> > > to
> > > the users should discourage misuse...
> >
> > I suspect a lack of inc_not_zero and dec_and_test would
> > be the biggest things discouraging misuse of stats_t
> > for reference counting :)
>
> Right, but it's the continuing atomic_t use that concerns me...
Can we remove inc_not_zero and dec_and_test functionality
from the atomic_t macros?
It would require fixing all of the in tree code, and after
that people with out of tree code would have to switch to
refcount_t to make their code work again.
--
All Rights Reversed.
Download attachment "signature.asc" of type "application/pgp-signature" (474 bytes)
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.
