From: Christian Borntraeger <borntraeger@de.ibm.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, paulmck@linux.vnet.ibm.com,
Christian Borntraeger <borntraeger@de.ibm.com>
Subject: [GIT PULL] disallow non-scalar accesses for ACCESS_ONCE
Date: Mon, 9 Feb 2015 11:22:46 +0100 [thread overview]
Message-ID: <1423477366-6066-1-git-send-email-borntraeger@de.ibm.com> (raw)
Linus,
The following changes since commit b1940cd21c0f4abdce101253e860feff547291b0:
Linux 3.19-rc3 (2015-01-05 17:05:20 -0800)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/borntraeger/linux.git tags/for-linus
for you to fetch changes up to c5b19946eb76c67566aae6a84bf2b10ad59295ea:
kernel: Fix sparse warning for ACCESS_ONCE (2015-01-19 14:15:00 +0100)
----------------------------------------------------------------
Tighten rules for ACCESS_ONCE
This series tightens the rules for ACCESS_ONCE to only work
on scalar types. It also contains the necessary fixups as
indicated by build bots of linux-next.
Now everything is in place to prevent new non-scalar users
of ACCESS_ONCE and we can continue to convert code to
READ_ONCE/WRITE_ONCE.
----------------------------------------------------------------
Christian Borntraeger (7):
ppc/kvm: Replace ACCESS_ONCE with READ_ONCE
ppc/hugetlbfs: Replace ACCESS_ONCE with READ_ONCE
x86/xen/p2m: Replace ACCESS_ONCE with READ_ONCE
x86/spinlock: Leftover conversion ACCESS_ONCE->READ_ONCE
mm/gup: Replace ACCESS_ONCE with READ_ONCE
kernel: tighten rules for ACCESS ONCE
kernel: Fix sparse warning for ACCESS_ONCE
Guenter Roeck (1):
next: sh: Fix compile error
arch/powerpc/kvm/book3s_hv_rm_xics.c | 8 ++++----
arch/powerpc/kvm/book3s_xics.c | 16 ++++++++--------
arch/powerpc/mm/hugetlbpage.c | 4 ++--
arch/sh/mm/gup.c | 2 +-
arch/x86/include/asm/spinlock.h | 4 ++--
arch/x86/xen/p2m.c | 2 +-
include/linux/compiler.h | 21 ++++++++++++++++-----
mm/gup.c | 2 +-
8 files changed, 35 insertions(+), 24 deletions(-)
reply other threads:[~2015-02-09 10:22 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1423477366-6066-1-git-send-email-borntraeger@de.ibm.com \
--to=borntraeger@de.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=paulmck@linux.vnet.ibm.com \
--cc=torvalds@linux-foundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®