linux-kernel - [PATCH tip/core/rcu 0/3] rcu: fix !PREEMPT, __mpol_dup(), and ftrace_perf_buf

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-next>] [day] [month] [year] [list]

Message-ID: <20100304015001.GA32190@linux.vnet.ibm.com>
Date:	Wed, 3 Mar 2010 17:50:01 -0800
From:	"Paul E. McKenney" <paulmck@...ux.vnet.ibm.com>
To:	linux-kernel@...r.kernel.org
Cc:	mingo@...e.hu, laijs@...fujitsu.com, dipankar@...ibm.com,
	akpm@...ux-foundation.org, mathieu.desnoyers@...ymtl.ca,
	josh@...htriplett.org, dvhltc@...ibm.com, niv@...ibm.com,
	tglx@...utronix.de, peterz@...radead.org, rostedt@...dmis.org,
	Valdis.Kletnieks@...edu, dhowells@...hat.com
Subject: [PATCH tip/core/rcu 0/3] rcu: fix !PREEMPT, __mpol_dup(), and
	ftrace_perf_buf_prepare() RCU lockdep splats

Hello!

This patch fixes three RCU lockdep issues:

1.	Makes rcu_read_lock_sched_held() correctly handle !PREEMPT
	kernels.

2.	Suppresses __mpol_dup() false positive.

3.	Converts a pair of rcu_dereference() calls in
	ftrace_perf_buf_prepare() to rcu_dereference_sched().

There are probably more where these came from.  ;-)

							Thanx, Paul

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

 include/linux/rcupdate.h           |   15 ++++++++++++++-
 include/trace/ftrace.h             |    4 ++--
 kernel/trace/trace_event_profile.c |    5 ++---
 mm/mempolicy.c                     |    3 ++-
 4 files changed, 20 insertions(+), 7 deletions(-)
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/