Lines Matching +full:sanitizers +full:- +full:linux

21 * Compile the patch with default and non-default configurations.
22   - Use sanitizers e.g. undefined behaviour, address.
23   - Compile on non-x86
24   - Compile on x86 with -m32
27   - Use single vCPU
28   - Use many vCPUs and enable NUMA
29   - Restrict RAM to < 1GB.
31 * Run effected tests on non-x86 machine in general
33 * Run tests with "-i0"
50   - Could future kernel behaviour change without "breaking userland"?
51   - Does the kernel behave differently depending on hardware?
52   - Does it behave differently depending on kernel configuration?
53   - Does it behave differently depending on the compiler?
54   - Would it behave differently if the order of checks on syscall parameters
57   - What happens if there are 100+ CPUs?
58   - What happens if each CPU core is very slow?
59   - What happens if there are 2TB of RAM?
64   - What happens if a process gets preempted?
65   - Could checkpoints or fuzzsync by used instead?
66   - Note, usually you can insert a sleep to prove a race condition
72 Once you think a patch is good enough you should add your Reviewed-by
73 and/or Tested-by tags. This means you will get some credit for getting
76 If you ran the test you can add the Tested-by tag. If you read the
77 code or used static analysis tools on it, you can add the Reviewed-by
95 * Author's `Signed-off-by` tag
96 * Committer's `Reviewed-by` or `Signed-off-by` tag
104 Also update `.github/workflows/wiki-mirror.yml` script which mirrors
105 `doc/*.txt` to LTP wiki (git URL https://github.com/linux-test-project/ltp.wiki.git)
113   (e.g. run with `-i 100`)
114 * Run with `-i 0` to check that setup and cleanup are coded properly (no test is being run)
117   GPL-2.0-or-later; the licence for test (e.g. GPL-2.0) should not change
122 * Use new https://github.com/linux-test-project/ltp/wiki/Test-Writing-Guidelines#22-writing-a-test-…
125 …(more in https://github.com/linux-test-project/ltp/wiki/Test-Writing-Guidelines#21-c-coding-style[…
128 …(more in https://github.com/linux-test-project/ltp/wiki/Test-Writing-Guidelines#2238-test-tags[Tes…
134 * Use new https://github.com/linux-test-project/ltp/wiki/Test-Writing-Guidelines#23-writing-a-testc…
136 …(more in https://github.com/linux-test-project/ltp/wiki/Test-Writing-Guidelines#132-shell-coding-s…
141 https://github.com/linux-test-project/ltp/wiki/LTP-Library-API-Writing-Guidelines[LTP Library API W…