~ [ source navigation ] ~ [ diff markup ] ~ [ identifier search ] ~

TOMOYO Linux Cross Reference
Linux/tools/testing/selftests/arm64/signal/README

Version: ~ [ linux-6.12-rc7 ] ~ [ linux-6.11.7 ] ~ [ linux-6.10.14 ] ~ [ linux-6.9.12 ] ~ [ linux-6.8.12 ] ~ [ linux-6.7.12 ] ~ [ linux-6.6.60 ] ~ [ linux-6.5.13 ] ~ [ linux-6.4.16 ] ~ [ linux-6.3.13 ] ~ [ linux-6.2.16 ] ~ [ linux-6.1.116 ] ~ [ linux-6.0.19 ] ~ [ linux-5.19.17 ] ~ [ linux-5.18.19 ] ~ [ linux-5.17.15 ] ~ [ linux-5.16.20 ] ~ [ linux-5.15.171 ] ~ [ linux-5.14.21 ] ~ [ linux-5.13.19 ] ~ [ linux-5.12.19 ] ~ [ linux-5.11.22 ] ~ [ linux-5.10.229 ] ~ [ linux-5.9.16 ] ~ [ linux-5.8.18 ] ~ [ linux-5.7.19 ] ~ [ linux-5.6.19 ] ~ [ linux-5.5.19 ] ~ [ linux-5.4.285 ] ~ [ linux-5.3.18 ] ~ [ linux-5.2.21 ] ~ [ linux-5.1.21 ] ~ [ linux-5.0.21 ] ~ [ linux-4.20.17 ] ~ [ linux-4.19.323 ] ~ [ linux-4.18.20 ] ~ [ linux-4.17.19 ] ~ [ linux-4.16.18 ] ~ [ linux-4.15.18 ] ~ [ linux-4.14.336 ] ~ [ linux-4.13.16 ] ~ [ linux-4.12.14 ] ~ [ linux-4.11.12 ] ~ [ linux-4.10.17 ] ~ [ linux-4.9.337 ] ~ [ linux-4.4.302 ] ~ [ linux-3.10.108 ] ~ [ linux-2.6.32.71 ] ~ [ linux-2.6.0 ] ~ [ linux-2.4.37.11 ] ~ [ unix-v6-master ] ~ [ ccs-tools-1.8.12 ] ~ [ policy-sample ] ~
Architecture: ~ [ i386 ] ~ [ alpha ] ~ [ m68k ] ~ [ mips ] ~ [ ppc ] ~ [ sparc ] ~ [ sparc64 ] ~

Diff markup

Differences between /tools/testing/selftests/arm64/signal/README (Version linux-6.12-rc7) and /tools/testing/selftests/arm64/signal/README (Version linux-2.6.0)


  1 KSelfTest arm64/signal/                           
  2 =======================                           
  3                                                   
  4 Signals Tests                                     
  5 +++++++++++++                                     
  6                                                   
  7 - Tests are built around a common main compila    
  8   enforces a standard sequence of operations n    
  9   signal-test (setup/trigger/run/result/cleanu    
 10                                                   
 11 - The above mentioned ops are configurable on     
 12   is described (and configured) using the desc    
 13                                                   
 14 - Each signal testcase is compiled into its ow    
 15   executable is used for each test since many     
 16   by receiving some kind of fatal signal from     
 17   to run each test unit in its own standalone     
 18   test from a clean slate.                        
 19                                                   
 20 - New tests can be simply defined in testcases    
 21   tdescr overriding all the defaults we wish t    
 22   custom run method is mandatory though)          
 23                                                   
 24 - Signals' test-cases hereafter defined belong    
 25   principal families:                             
 26                                                   
 27   - 'mangle_' tests: a real signal (SIGUSR1) i    
 28     and then the test case code modifies the s    
 29     signal handler itself.                        
 30                                                   
 31   - 'fake_sigreturn_' tests: a brand new custo    
 32     is placed on the stack and a sigreturn sys    
 33     real signal return. This kind of tests doe    
 34     they are just fired using some simple incl    
 35                                                   
 36  - Most of these tests are successfully passin    
 37    some fatal signal: usually SIGSEGV or SIGBU    
 38    kind of tests it is extremely easy in fact     
 39    unrelated SEGV bugs in the testcases, it be    
 40    be really sure that the tests are really ad    
 41    to address and they are not instead falling    
 42    in the test code.                              
 43    In order to alleviate the misery of the lif    
 44    helpers are provided:                          
 45                                                   
 46    - a couple of ASSERT_BAD/GOOD_CONTEXT() mac    
 47      and verify if it is indeed GOOD or BAD (d    
 48      expecting), using the same logic/perspect    
 49      routines.                                    
 50                                                   
 51    - a sanity mechanism to be used in 'fake_si    
 52      default it takes care to verify that the     
 53      successfully progressed up to the stage o    
 54      call.                                        
 55                                                   
 56   In both cases test results are expected in t    
 57    - some fatal signal sent by the Kernel to t    
 58   or                                              
 59   - analyzing some final regs state               
                                                      

~ [ source navigation ] ~ [ diff markup ] ~ [ identifier search ] ~

kernel.org | git.kernel.org | LWN.net | Project Home | SVN repository | Mail admin

Linux® is a registered trademark of Linus Torvalds in the United States and other countries.
TOMOYO® is a registered trademark of NTT DATA CORPORATION.

sflogo.php