From: Peter Zijlstra <peterz@infradead.org>
To: mingo@kernel.org, paulmck@linux.vnet.ibm.com,
torvalds@linux-foundation.org, akpm@linux-foundation.org,
hpa@zytor.com, chris@chris-wilson.co.uk, nhaehnle@gmail.com,
linux-kernel@vger.kernel.org, dev@mblankhorst.nl,
tglx@linutronix.de
Cc: linux-tip-commits@vger.kernel.org
Subject: Re: [tip:locking/core] locking/ww_mutex: Add kselftests for ww_mutex stress
Date: Thu, 19 Jan 2017 21:13:03 +0100 [thread overview]
Message-ID: <20170119201303.GO6485@twins.programming.kicks-ass.net> (raw)
In-Reply-To: <tip-2a0c11282881875dc44f166a20eedf0d866dd0ef@git.kernel.org>
Hi Chris,
I got me this... I'm still trying to wrap my head around what exactly
the test does.
=====================================
[ BUG: bad unlock balance detected! ]
4.10.0-rc4-00122-g6edad167-dirty #608 Not tainted
-------------------------------------
kworker/u81:37/330 is trying to release lock (ww_class_mutex) at:
[<ffffffff8115260a>] stress_inorder_work+0x15a/0x330
but there are no more locks to release!
other info that might help us debug this:
4 locks held by kworker/u81:37/330:
#0: ("test-ww_mutex"){++++.+}, at: [<ffffffff81111d62>] process_one_work+0x1f2/0x710
#1: ((&stress->work)){+.+.+.}, at: [<ffffffff81111d62>] process_one_work+0x1f2/0x710
#2: (ww_class_acquire){+.+...}, at: [<ffffffff81111ddd>] process_one_work+0x26d/0x710
#3: (ww_class_mutex){+.+...}, at: [<ffffffff811525ba>] stress_inorder_work+0x10a/0x330
stack backtrace:
CPU: 22 PID: 330 Comm: kworker/u81:37 Not tainted 4.10.0-rc4-00122-g6edad167-dirty #608
Hardware name: Intel Corporation S2600GZ/S2600GZ, BIOS SE5C600.86B.02.02.0002.122320131210 12/23/2013
Workqueue: test-ww_mutex stress_inorder_work
Call Trace:
dump_stack+0x86/0xc3
? stress_inorder_work+0x15a/0x330
print_unlock_imbalance_bug+0xd8/0xe0
? stress_inorder_work+0x15a/0x330
lock_release+0x374/0x4b0
? schedule_hrtimeout_range_clock+0xda/0x270
__mutex_unlock_slowpath+0x43/0x2e0
ww_mutex_unlock+0x47/0xb0
stress_inorder_work+0x15a/0x330
? process_one_work+0x26d/0x710
process_one_work+0x26d/0x710
? process_one_work+0x1f2/0x710
worker_thread+0x48/0x4e0
kthread+0x101/0x140
? process_one_work+0x710/0x710
? kthread_create_on_node+0x40/0x40
ret_from_fork+0x31/0x40
INFO: task swapper/0:1 blocked for more than 120 seconds.
Not tainted 4.10.0-rc4-00122-g6edad167-dirty #608
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
swapper/0 D 0 1 0 0x00000000
Call Trace:
__schedule+0x30a/0xc60
schedule+0x40/0x90
schedule_timeout+0x30a/0x670
? wait_for_completion+0x23/0x100
? trace_hardirqs_on_caller+0x100/0x1c0
wait_for_completion+0x97/0x100
? wake_up_q+0x70/0x70
flush_workqueue+0x1f6/0x6b0
? flush_workqueue+0xe8/0x6b0
stress+0x1b3/0x203
test_ww_mutex_init+0x30a/0x324
? __pv_init_lock_hash+0x59/0x59
? set_debug_rodata+0x12/0x12
do_one_initcall+0x43/0x180
? set_debug_rodata+0x12/0x12
kernel_init_freeable+0x1d9/0x266
? rest_init+0x140/0x140
kernel_init+0xe/0x100
ret_from_fork+0x31/0x40
INFO: lockdep is turned off. +
next prev parent reply other threads:[~2017-01-19 20:13 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-01 11:47 locking: Add kselftests for ww_mutex Chris Wilson
2016-12-01 11:47 ` [PATCH v2 1/8] locking: Fix compilation of __WW_MUTEX_INITIALIZER Chris Wilson
2016-12-16 14:50 ` Peter Zijlstra
2016-12-16 17:26 ` Chris Wilson
2017-01-14 12:52 ` [tip:locking/core] locking/ww_mutex: " tip-bot for Chris Wilson
2016-12-01 11:47 ` [PATCH v2 2/8] locking: Add ww_mutex to locktorture test Chris Wilson
2017-01-14 12:52 ` [tip:locking/core] locking/ww_mutex: " tip-bot for Chris Wilson
2016-12-01 11:47 ` [PATCH v2 3/8] locking: Begin kselftests for ww_mutex Chris Wilson
2017-01-14 12:53 ` [tip:locking/core] locking/ww_mutex: " tip-bot for Chris Wilson
2016-12-01 11:47 ` [PATCH v2 4/8] locking: Add kselftests for ww_mutex AA deadlock detection Chris Wilson
2017-01-14 12:54 ` [tip:locking/core] locking/ww_mutex: " tip-bot for Chris Wilson
2016-12-01 11:47 ` [PATCH v2 5/8] locking: Add kselftests for ww_mutex ABBA " Chris Wilson
2017-01-14 12:54 ` [tip:locking/core] locking/ww_mutex: " tip-bot for Chris Wilson
2016-12-01 11:47 ` [PATCH v2 6/8] locking: Add kselftests for resolving ww_mutex cyclic deadlocks Chris Wilson
2017-01-14 12:55 ` [tip:locking/core] locking/ww_mutex: " tip-bot for Chris Wilson
2016-12-01 11:47 ` [PATCH v2 7/8] locking: Add kselftests for ww_mutex stress Chris Wilson
2017-01-14 12:55 ` [tip:locking/core] locking/ww_mutex: " tip-bot for Chris Wilson
2017-01-19 20:13 ` Peter Zijlstra [this message]
2016-12-01 11:47 ` [PATCH v2 8/8] locking: Add ww_mutex to tools/testing/selftests Chris Wilson
2017-01-14 12:56 ` [tip:locking/core] locking/ww_mutex: " tip-bot for Chris Wilson
2017-02-22 14:29 ` locking: Add kselftests for ww_mutex Geert Uytterhoeven
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=20170119201303.GO6485@twins.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=akpm@linux-foundation.org \
--cc=chris@chris-wilson.co.uk \
--cc=dev@mblankhorst.nl \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=nhaehnle@gmail.com \
--cc=paulmck@linux.vnet.ibm.com \
--cc=tglx@linutronix.de \
--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
Powered by JetHome