summaryrefslogtreecommitdiffstats
path: root/drivers/mtd/tests/torturetest.c
diff options
context:
space:
mode:
authorRichard Weinberger <richard@nod.at>2015-03-29 21:52:06 +0200
committerBrian Norris <computersforpeace@gmail.com>2015-04-05 18:12:53 -0700
commit2a6a28e7922c07c116ba8f2aa3682c03ef8be678 (patch)
treea12044a676ee8b2b3668b6e1bcffae46180befb1 /drivers/mtd/tests/torturetest.c
parentd2b51c808745ca93c020ba34a3cf256ad52adc63 (diff)
downloadlinux-2a6a28e7922c07c116ba8f2aa3682c03ef8be678.tar.bz2
mtd: Make MTD tests cancelable
I always go nuts when I start an MTD test on a slow device and have to wait forever until it finishes. From the debug output I already know what the issue is but I have to wait or reset the board hard. Resetting is often not an option (remote access, you don't want lose the current state, etc...). The solution is easy, check for pending signals at key positions in the code. Using that one can even stop a test by pressing CTRL-C as insmod/modprobe have SIGINT pending. Signed-off-by: Richard Weinberger <richard@nod.at> Signed-off-by: Brian Norris <computersforpeace@gmail.com>
Diffstat (limited to 'drivers/mtd/tests/torturetest.c')
-rw-r--r--drivers/mtd/tests/torturetest.c15
1 files changed, 12 insertions, 3 deletions
diff --git a/drivers/mtd/tests/torturetest.c b/drivers/mtd/tests/torturetest.c
index 5045cf1b3160..e5d6e6d9532f 100644
--- a/drivers/mtd/tests/torturetest.c
+++ b/drivers/mtd/tests/torturetest.c
@@ -279,7 +279,10 @@ static int __init tort_init(void)
" for 0xFF... pattern\n");
goto out;
}
- cond_resched();
+
+ err = mtdtest_relax();
+ if (err)
+ goto out;
}
}
@@ -294,7 +297,10 @@ static int __init tort_init(void)
err = write_pattern(i, patt);
if (err)
goto out;
- cond_resched();
+
+ err = mtdtest_relax();
+ if (err)
+ goto out;
}
/* Verify what we wrote */
@@ -314,7 +320,10 @@ static int __init tort_init(void)
"0x55AA55..." : "0xAA55AA...");
goto out;
}
- cond_resched();
+
+ err = mtdtest_relax();
+ if (err)
+ goto out;
}
}