Cyril Hrubis

@acerv FYI this is something that should go into the new testrunner later on.

Looking at the list the first in.py is actually a datafile that is being used by the file command tests no need to do anything about it. As for the...

The basic tests were merged but the functional test from @amannch was send to ML but wasn't 100% finished, the code and discussion could be seen here: https://lists.linux.it/pipermail/ltp/2019-July/012943.html

This has been superseded by 877b445c9155f7c27453524239c7019068e99e67

@padmashree9110 if you are going to work on LTP it's probably a good idea to subscribe to the mailing list and read messages related to your tests there.

There are many other problems in there, apart from the missing check for the syscall existence. These tests are written so that they are all executed by a single script,...

Looking at the code it indeed does not seem to work when number of CPUs is higher than maximal sched_priority. I suppose that the test needs redesign.

The bug should be fixed with: https://marc.info/?l=linux-kernel&m=152460926619256

Also the scenarios where the memory is backed up by a file should be executed against all supported filesystems to make sure the allocation is done correctly.

This is halfway done, some of the problematic tests were rewritten into C and removed from the numa01.sh test.