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]
Date:   Wed, 13 Jan 2021 10:56:44 +0000
From:   David Howells <dhowells@...hat.com>
To:     Casey Schaufler <casey@...aufler-ca.com>
Cc:     dhowells@...hat.com, pnagar@...eaurora.org, arnd@...db.de,
        jmorris@...ei.org, serge@...lyn.com, paul@...l-moore.com,
        stephen.smalley.work@...il.com, eparis@...isplace.org,
        linux-security-module@...r.kernel.org, selinux@...r.kernel.org,
        linux-arch@...r.kernel.org, psodagud@...eaurora.org,
        nmardana@...eaurora.org, dsule@...eaurora.org,
        Joe Perches <joe@...ches.com>, Miguel Ojeda <ojeda@...nel.org>,
        Nick Desaulniers <ndesaulniers@...gle.com>,
        linux-kernel@...r.kernel.org
Subject: Re: [RFC PATCH v2] selinux: security: Move selinux_state to a separate page

Casey Schaufler <casey@...aufler-ca.com> wrote:

> >> How would this interact with or complement __read_mostly?
> >>
> > Currently, the mechanism we are working on developing is
> > independent of __read_mostly. This is something we can look more into
> > while working further on the mechanism.
> 
> Please either integrate the two or explain how they differ.
> It appears that you haven't considered how you might exploit
> or expand the existing mechanism.

I think __read_mostly is about grouping stuff together that's rarely going to
be read to make the CPU's data cache more efficient.  It doesn't stop people
writing to such a variable.

David

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ