locking/locktorture: Fix rwsem reader_delay
authorDavidlohr Bueso <dave@stgolabs.net>
Mon, 15 May 2017 09:07:22 +0000 (02:07 -0700)
committerPaul E. McKenney <paulmck@linux.vnet.ibm.com>
Mon, 11 Dec 2017 17:18:28 +0000 (09:18 -0800)
We should account for nreader threads, not writers in this
callback. Could even trigger a div by 0 if the user explicitly
disables writers.

Signed-off-by: Davidlohr Bueso <dbueso@suse.de>
Signed-off-by: Paul E. McKenney <paulmck@linux.vnet.ibm.com>
kernel/locking/locktorture.c

index 617cea2520b3fe8c61400de8541f60f33d650f07..a307a79e6b0b97e8f84eb81d414b31dba23f1415 100644 (file)
@@ -560,7 +560,7 @@ static void torture_rwsem_read_delay(struct torture_random_state *trsp)
 
        /* We want a long delay occasionally to force massive contention.  */
        if (!(torture_random(trsp) %
-             (cxt.nrealwriters_stress * 2000 * longdelay_ms)))
+             (cxt.nrealreaders_stress * 2000 * longdelay_ms)))
                mdelay(longdelay_ms * 2);
        else
                mdelay(longdelay_ms / 2);