Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.kernel > #1578404 > unrolled thread

Re: [PATCH] security: use READ_ONCE instead of deprecated ACCESS_ONCE

Started byDavid Howells <dhowells@redhat.com>
First post2017-02-10 12:30 +0100
Last post2017-02-10 12:30 +0100
Articles 1 — 1 participant

Back to article view | Back to linux.kernel

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.


Contents

  Re: [PATCH] security: use READ_ONCE instead of deprecated ACCESS_ONCE David Howells <dhowells@redhat.com> - 2017-02-10 12:30 +0100

#1578404 — Re: [PATCH] security: use READ_ONCE instead of deprecated ACCESS_ONCE

FromDavid Howells <dhowells@redhat.com>
Date2017-02-10 12:30 +0100
SubjectRe: [PATCH] security: use READ_ONCE instead of deprecated ACCESS_ONCE
Message-ID<t9hyN-2L5-3@gated-at.bofh.it>
Davidlohr Bueso <dave@stgolabs.net> wrote:

> With the new standardized functions, we can replace all ACCESS_ONCE()
> calls across relevant security/keyrings/.
> 
> ACCESS_ONCE() does not work reliably on non-scalar types. For example
> gcc 4.6 and 4.7 might remove the volatile tag for such accesses during
> the SRA (scalar replacement of aggregates) step:
> 
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=58145
> 
> Update the new calls regardless of if it is a scalar type, this is
> cleaner than having three alternatives.
> 
> Signed-off-by: Davidlohr Bueso <dbueso@suse.de>

Applied.

[toc] | [standalone]


Back to top | Article view | linux.kernel


csiph-web