From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: linux-kernel@vger.kernel.org
Cc: mingo@kernel.org, jiangshanlai@gmail.com, dipankar@in.ibm.com,
akpm@linux-foundation.org, mathieu.desnoyers@efficios.com,
josh@joshtriplett.org, tglx@linutronix.de, peterz@infradead.org,
rostedt@goodmis.org, dhowells@redhat.com, edumazet@google.com,
dvhart@linux.intel.com, fweisbec@gmail.com, oleg@redhat.com,
bobby.prani@gmail.com
Subject: [PATCH tip/core/rcu 0/7] RCU list updates for 4.9
Date: Mon, 22 Aug 2016 08:45:01 -0700 [thread overview]
Message-ID: <20160822154501.GA10364@linux.vnet.ibm.com> (raw)
Hello!
This series provides updates to RCU-protected linked lists:
1. Expand list_first_entry_or_null() to allow better compiler
optimizations, courtesy of Chris Wilson.
2-6. Allow security-conscious builds to specify BUG rather than WARN
for linked-list corruption, courtesy of Kees Cook.
7. Fix a bogus CONFIG_-prefixed Kconfig-option reference in #5
above, courtesy of Valentin Rothberg.
Thanx, Paul
next reply other threads:[~2016-08-22 15:45 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-22 15:45 Paul E. McKenney [this message]
2016-08-22 15:45 ` [PATCH tip/core/rcu 1/7] list: Expand list_first_entry_or_null() Paul E. McKenney
2016-08-22 15:45 ` [PATCH tip/core/rcu 2/7] list: Split list_add() debug checking into separate function Paul E. McKenney
2016-08-22 15:45 ` [PATCH tip/core/rcu 3/7] rculist: Consolidate DEBUG_LIST for list_add_rcu() Paul E. McKenney
2016-08-22 15:45 ` [PATCH tip/core/rcu 4/7] list: Split list_del() debug checking into separate function Paul E. McKenney
2016-08-22 15:45 ` [PATCH tip/core/rcu 5/7] bug: Provide toggle for BUG on data corruption Paul E. McKenney
2016-08-22 15:45 ` [PATCH tip/core/rcu 6/7] lkdtm: Add tests for struct list corruption Paul E. McKenney
2016-08-22 15:45 ` [PATCH tip/core/rcu 7/7] lib/Kconfig.debug: Fix typo in select statement Paul E. McKenney
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=20160822154501.GA10364@linux.vnet.ibm.com \
--to=paulmck@linux.vnet.ibm.com \
--cc=akpm@linux-foundation.org \
--cc=bobby.prani@gmail.com \
--cc=dhowells@redhat.com \
--cc=dipankar@in.ibm.com \
--cc=dvhart@linux.intel.com \
--cc=edumazet@google.com \
--cc=fweisbec@gmail.com \
--cc=jiangshanlai@gmail.com \
--cc=josh@joshtriplett.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=mingo@kernel.org \
--cc=oleg@redhat.com \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=tglx@linutronix.de \
/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