Changes

| kernel || Fix VDSO remapping on non-x86 architectures || medium || Laurent Dufour, cov || However some architectures like PowerPC and ARM are keeping a reference to the VDSO base address to build the signal return stack frame by calling the VDSO sigreturn service. So once the VDSO has been moved, this reference is no more valid and the signal frame built later are not usable.

| kernel || Fix VDSO remapping on non-x86 architectures || medium || Laurent Dufour, cov || However some architectures like PowerPC and ARM are keeping a reference to the VDSO base address to build the signal return stack frame by calling the VDSO sigreturn service. So once the VDSO has been moved, this reference is no more valid and the signal frame built later are not usable.

|-

|-

| tests || Run many/all tests in "container" || medium || - || -

| tests || Run many/all tests in "container" || medium || - || Currently we run zdtm tests one-by-one. It would be nice to run the all in one pseudo-container and C/R them as one big subtree.

|-

|-

| tests || Trinity-like (fuzz) testing || hard || - || -

| tests || Trinity-like (fuzz) testing || hard || - || The existing suite is 99% functionality testing. Need more sophisticated testing -- take a process that has done a random set of actions, C/R one, check that all is OK. The latter is the most complicated thing.

|-

|-

| tests || Split mountpoints.c test into pieces || easy || - || -

| tests || Split mountpoints.c test into pieces || easy || - || Currently this one is one big set of tests. Need more fine-grained set.

|-

|-

| tests ||  

| tests/infrastructure || Run tests on patches sent to the mailing lists || medium || - || It's quite typical that a set sent to the mailing list fails some tests. Need a robot that would monitor the list, check the patches and send the result back.

|}

|}

[[Category:Development]]

[[Category:Development]]

[[Category:Plans]]

[[Category:Plans]]