locking/locktorture: Fix num reader/writer corner cases
authorDavidlohr Bueso <dave@stgolabs.net>
Mon, 15 May 2017 09:07:23 +0000 (02:07 -0700)
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>
Mon, 19 Mar 2018 07:42:56 +0000 (08:42 +0100)
commitc02dd004559c8ca6e3c1e924e2abafb0e000ffae
tree75b6f44d766d983a07cbc10265e239624d9fb076
parent09e59383eb1c1a3b45ba7bb131af5ea936868752
locking/locktorture: Fix num reader/writer corner cases

[ Upstream commit 2ce77d16db4240dd2e422fc0a5c26d3e2ec03446 ]

Things can explode for locktorture if the user does combinations
of nwriters_stress=0 nreaders_stress=0. Fix this by not assuming
we always want to torture writer threads.

Reported-by: Jeremy Linton <jeremy.linton@arm.com>
Signed-off-by: Davidlohr Bueso <dbueso@suse.de>
Signed-off-by: Paul E. McKenney <paulmck@linux.vnet.ibm.com>
Reviewed-by: Jeremy Linton <jeremy.linton@arm.com>
Tested-by: Jeremy Linton <jeremy.linton@arm.com>
Signed-off-by: Sasha Levin <alexander.levin@microsoft.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
kernel/locking/locktorture.c