diff options
| author | Kees Cook <keescook@chromium.org> | 2017-04-24 13:23:21 -0700 |
|---|---|---|
| committer | Kees Cook <keescook@chromium.org> | 2017-07-26 14:38:03 -0700 |
| commit | 95925c99b9043d52db626645e6ef5ee5f62c97e4 (patch) | |
| tree | c7aca11aba82dbf05d5b75e5655be29f0b92bc90 /net | |
| parent | 520eccdfe187591a51ea9ab4c1a024ae4d0f68d9 (diff) | |
| download | linux-95925c99b9043d52db626645e6ef5ee5f62c97e4.tar.bz2 | |
lkdtm: Provide more complete coverage for REFCOUNT tests
The existing REFCOUNT_* LKDTM tests were designed only for testing a narrow
portion of CONFIG_REFCOUNT_FULL. This moves the tests to their own file and
expands their testing to poke each boundary condition.
Since the protections (CONFIG_REFCOUNT_FULL and x86-fast) use different
saturation values and reach-zero behavior, those have to be build-time
set so the tests can actually validate things are happening at the
right places.
Notably, the x86-fast protection will fail REFCOUNT_INC_ZERO and
REFCOUNT_ADD_ZERO since those conditions are not checked (only overflow
is critical to protecting refcount_t). CONFIG_REFCOUNT_FULL will warn for
each REFCOUNT_*_NEGATIVE test since it provides zero-pinning behaviors
(which allows it to pass REFCOUNT_INC_ZERO and REFCOUNT_ADD_ZERO).
Signed-off-by: Kees Cook <keescook@chromium.org>
Diffstat (limited to 'net')
0 files changed, 0 insertions, 0 deletions