All of lore.kernel.org
 help / color / mirror / Atom feed
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/4] linked-list updates for 4.5
Date: Fri, 4 Dec 2015 16:15:05 -0800	[thread overview]
Message-ID: <20151205001505.GA26649@linux.vnet.ibm.com> (raw)

Hello!

This series contains a few linked-list updates:

1.	Use WRITE_ONCE() when adding to lists and hlists (reported
	by KTSAN).

2.	Use READ_ONCE() when testing for empty lists (reported by
	KTSAN).

3.	Introduce generic list_splice_tail_init_rcu(), courtesy of
	Petko Manolov.

4.	Use WRITE_ONCE() when initializing list_head structures (reported
	by KTSAN).

							Thanx, Paul

------------------------------------------------------------------------

 b/include/linux/list.h       |   14 ++++----
 b/include/linux/list_bl.h    |    2 -
 b/include/linux/list_nulls.h |    2 -
 b/include/linux/rculist.h    |   69 ++++++++++++++++++++++++++++++-------------
 b/lib/list_debug.c           |    2 -
 5 files changed, 59 insertions(+), 30 deletions(-)


             reply	other threads:[~2015-12-05  0:14 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-05  0:15 Paul E. McKenney [this message]
2015-12-05  0:15 ` [PATCH tip/core/rcu 1/4] list: Use WRITE_ONCE() when adding to lists and hlists Paul E. McKenney
2015-12-05  0:15 ` [PATCH tip/core/rcu 2/4] list: Use READ_ONCE() when testing for empty lists Paul E. McKenney
2015-12-05  0:15 ` [PATCH tip/core/rcu 3/4] list: Introduces generic list_splice_tail_init_rcu() Paul E. McKenney
2015-12-05  0:15 ` [PATCH tip/core/rcu 4/4] list: Use WRITE_ONCE() when initializing list_head structures 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=20151205001505.GA26649@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.