diff options
| author | Richard Weinberger <richard@nod.at> | 2015-03-29 22:52:06 +0300 |
|---|---|---|
| committer | Brian Norris <computersforpeace@gmail.com> | 2015-04-06 04:12:53 +0300 |
| commit | 2a6a28e7922c07c116ba8f2aa3682c03ef8be678 (patch) | |
| tree | a12044a676ee8b2b3668b6e1bcffae46180befb1 /drivers/mtd/tests/pagetest.c | |
| parent | d2b51c808745ca93c020ba34a3cf256ad52adc63 (diff) | |
| download | linux-2a6a28e7922c07c116ba8f2aa3682c03ef8be678.tar.xz | |
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/pagetest.c')
| -rw-r--r-- | drivers/mtd/tests/pagetest.c | 10 |
1 files changed, 8 insertions, 2 deletions
diff --git a/drivers/mtd/tests/pagetest.c b/drivers/mtd/tests/pagetest.c index 88296e888e9d..ba1890d5632c 100644 --- a/drivers/mtd/tests/pagetest.c +++ b/drivers/mtd/tests/pagetest.c @@ -407,7 +407,10 @@ static int __init mtd_pagetest_init(void) goto out; if (i % 256 == 0) pr_info("written up to eraseblock %u\n", i); - cond_resched(); + + err = mtdtest_relax(); + if (err) + goto out; } pr_info("written %u eraseblocks\n", i); @@ -422,7 +425,10 @@ static int __init mtd_pagetest_init(void) goto out; if (i % 256 == 0) pr_info("verified up to eraseblock %u\n", i); - cond_resched(); + + err = mtdtest_relax(); + if (err) + goto out; } pr_info("verified %u eraseblocks\n", i); |