linux-kernel - Re: [PATCH RFC] mm: Rename SLAB_DESTROY_BY_RCU to SLAB_TYPESAFE_BY

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <alpine.DEB.2.20.1701251045040.983@east.gentwo.org>
Date:   Wed, 25 Jan 2017 10:45:52 -0600 (CST)
From:   Christoph Lameter <cl@...ux.com>
To:     "Paul E. McKenney" <paulmck@...ux.vnet.ibm.com>
cc:     willy@...radead.org, linux-kernel@...r.kernel.org,
        linux-mm@...ck.org, penberg@...nel.org, rientjes@...gle.com,
        iamjoonsoo.kim@....com, akpm@...ux-foundation.org
Subject: Re: [PATCH RFC] mm: Rename SLAB_DESTROY_BY_RCU to
 SLAB_TYPESAFE_BY_RCU

On Sun, 22 Jan 2017, Paul E. McKenney wrote:

> On Wed, Jan 18, 2017 at 06:00:24PM -0600, Christoph Lameter wrote:
> > On Wed, 18 Jan 2017, Paul E. McKenney wrote:
> >
> > > Actually, slab is using RCU to provide type safety to those slab users
> > > who request it.
> >
> > Typesafety is a side effect. The main idea here is that the object can
> > still be accessed in RCU sections after another processor frees the
> > object. We guarantee that the object is not freed but it may be reused
> > for another object within the RCU period.
> >
> > Can we have a name that expresses all of that properly?
>
> But of course!!!  "Type safety".  http://wiki.c2.com/?TypeSafe

Well that does not convey the idea that RCU is involved here.

SLAB_DESTROY_RCU_TYPESAFE

?