From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: linux-kernel@vger.kernel.org
Cc: mingo@kernel.org, laijs@cn.fujitsu.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,
"Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
Subject: [PATCH tip/core/rcu 07/11] rcutorture: Specify CONFIG_CPUMASK_OFFSTACK=y for TREE07
Date: Thu, 28 Aug 2014 12:12:19 -0700 [thread overview]
Message-ID: <1409253143-31466-7-git-send-email-paulmck@linux.vnet.ibm.com> (raw)
In-Reply-To: <1409253143-31466-1-git-send-email-paulmck@linux.vnet.ibm.com>
From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
This commit specifies offstack cpumasks in TREE07 in order to catch
references to unallocated cpumask_var_t variables.
Signed-off-by: Paul E. McKenney <paulmck@linux.vnet.ibm.com>
---
tools/testing/selftests/rcutorture/configs/rcu/TREE07 | 1 +
1 file changed, 1 insertion(+)
diff --git a/tools/testing/selftests/rcutorture/configs/rcu/TREE07 b/tools/testing/selftests/rcutorture/configs/rcu/TREE07
index 715ee5e0d59d..8f1017666aa7 100644
--- a/tools/testing/selftests/rcutorture/configs/rcu/TREE07
+++ b/tools/testing/selftests/rcutorture/configs/rcu/TREE07
@@ -1,5 +1,6 @@
CONFIG_SMP=y
CONFIG_NR_CPUS=16
+CONFIG_CPUMASK_OFFSTACK=y
CONFIG_PREEMPT_NONE=y
CONFIG_PREEMPT_VOLUNTARY=n
CONFIG_PREEMPT=n
--
1.8.1.5
next prev parent reply other threads:[~2014-08-28 19:13 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-28 19:12 [PATCH tip/core/rcu 0/11] Torture-test changes for 3.18 Paul E. McKenney
2014-08-28 19:12 ` [PATCH tip/core/rcu 01/11] rcutorture: Fix a sparse warning by marking boost_mutex static Paul E. McKenney
2014-08-28 19:12 ` [PATCH tip/core/rcu 02/11] rcutorture: Use bash shell for all the test scripts Paul E. McKenney
2014-08-28 19:12 ` [PATCH tip/core/rcu 03/11] rcutorture: Set executable bit and drop bash from Usage Paul E. McKenney
2014-08-28 19:12 ` [PATCH tip/core/rcu 04/11] rcu: Add step to initrd documentation Paul E. McKenney
2014-08-28 19:12 ` [PATCH tip/core/rcu 05/11] rcutorture: Test partial nohz_full= configuration Paul E. McKenney
2014-08-28 19:12 ` [PATCH tip/core/rcu 06/11] rcutorture: Specify MAXSMP=y for TREE01 Paul E. McKenney
2014-08-28 19:12 ` Paul E. McKenney [this message]
2014-08-28 19:12 ` [PATCH tip/core/rcu 08/11] rcu: Use pr_alert/pr_cont for printing logs Paul E. McKenney
2014-08-28 19:12 ` [PATCH tip/core/rcu 09/11] rcutorture: Add callback-flood test Paul E. McKenney
2014-08-28 19:12 ` [PATCH tip/core/rcu 10/11] torture: Print PID in hung-kernel diagnostic message Paul E. McKenney
2014-08-28 19:12 ` [PATCH tip/core/rcu 11/11] torture: Check for nul bytes in console output Paul E. McKenney
2014-09-07 17:09 ` [PATCH tip/core/rcu 0/11] Torture-test changes for 3.18 Pranith Kumar
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=1409253143-31466-7-git-send-email-paulmck@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=josh@joshtriplett.org \
--cc=laijs@cn.fujitsu.com \
--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;
as well as URLs for NNTP newsgroup(s).