| Message ID | 20220725100641.11625-3-rpalethorpe@suse.com |
|---|---|
| State | Accepted |
| Headers | show |
| Series | [v2,1/4] read_all: Add worker timeout and rewrite scheduling | expand |
Reviewed-by: Li Wang <liwang@redhat.com>
diff --git a/testcases/kernel/fs/read_all/read_all.c b/testcases/kernel/fs/read_all/read_all.c index 02c8f1754..c36203846 100644 --- a/testcases/kernel/fs/read_all/read_all.c +++ b/testcases/kernel/fs/read_all/read_all.c @@ -95,7 +95,6 @@ static int timeout_warnings_left = 15; static char *blacklist[] = { NULL, /* reserved for -e parameter */ - "/sys/power/wakeup_count", "/sys/kernel/debug/*", "/sys/devices/platform/*/eeprom", "/sys/devices/platform/*/nvmem",
This was filtered because it could block at certain times. However we will now kill the worker and continue. This could still result in a TBROK test failure if the process can't be killed (quick enough). Possibly this can be considered a kernel bug because reading this file should not make an unprivileged process unkillable. Or else the tester needs to increase LTP_RUNTIME_MUL. Signed-off-by: Richard Palethorpe <rpalethorpe@suse.com> --- IMO debug is the only legitimate blacklist item. There's nothing special about cpu, eeprom or nvmem, any hardware could cause these issues. testcases/kernel/fs/read_all/read_all.c | 1 - 1 file changed, 1 deletion(-)