From mboxrd@z Thu Jan 1 00:00:00 1970 Reply-To: kernel-hardening@lists.openwall.com Message-ID: <1479316156.21171.30.camel@redhat.com> From: Rik van Riel Date: Wed, 16 Nov 2016 12:09:16 -0500 In-Reply-To: References: <20161110203749.GV3117@twins.programming.kicks-ass.net> <20161110204838.GE17134@arm.com> <20161110211310.GX3117@twins.programming.kicks-ass.net> <20161110222744.GD8086@kroah.com> <20161110233835.GA23164@kroah.com> <20161111174630.GO3117@twins.programming.kicks-ass.net> <20161111201704.GQ3117@twins.programming.kicks-ass.net> <1479228602.4622.64.camel@redhat.com> Content-Type: multipart/signed; micalg="pgp-sha256"; protocol="application/pgp-signature"; boundary="=-jEQ7m7/KpQV8pNnjFgLW" Mime-Version: 1.0 Subject: Re: [kernel-hardening] Re: [RFC v4 PATCH 00/13] HARDENED_ATOMIC To: kernel-hardening@lists.openwall.com Cc: Peter Zijlstra , Will Deacon , Greg KH , David Windsor , Elena Reshetova , Arnd Bergmann , Thomas Gleixner , Ingo Molnar , "H. Peter Anvin" List-ID: --=-jEQ7m7/KpQV8pNnjFgLW Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Tue, 2016-11-15 at 09:23 -0800, Kees Cook wrote: > On Tue, Nov 15, 2016 at 8:50 AM, Rik van Riel > wrote: > >=20 > > On Mon, 2016-11-14 at 12:31 -0800, Kees Cook wrote: > > >=C2=A0 > > > Keeping the implementation details of refcount_t and stats_t > > > opaque > > > to > > > the users should discourage misuse... > >=20 > > 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 :) >=20 > 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. --=20 All Rights Reversed. --=-jEQ7m7/KpQV8pNnjFgLW Content-Type: application/pgp-signature; name="signature.asc" Content-Description: This is a digitally signed message part Content-Transfer-Encoding: 7bit -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQEcBAABCAAGBQJYLJK9AAoJEM553pKExN6DBF0H/39RZS2SnbsqIBYexNGRiT8O Ym5QHl+1OEKzbNnKPAdpnz/in/a73bXIoyqvC5OCvgrIuHwl4+MQYZ+nxUg+ozBK 0pSHfoDpN93kR+kftCGqyL89QB8y1QGMjiEGFVKWZfyG3Wt+vSYP925i4AxAEeP2 VP2a2YJMFREcGrsdoti7/wPqSqU1c4ZbdEGC/xa0/QmZ2EYTzRVuI0+Ox2Fq5Vvc gf/ECefMQLJkny2ucE952FZd9SS26HA/bVQtsd3jKJdPJEmKIcj7/Jz9xHrF9dPu 4m+frjggCat6feP7d6/LryWG72cqWK3ngSra8YKVvj9VrUyNimV02qL5rDijvPs= =fsUO -----END PGP SIGNATURE----- --=-jEQ7m7/KpQV8pNnjFgLW--