lkml.org 
[lkml]   [2021]   [Jan]   [4]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    /
    Date
    From
    SubjectRe: [PATCH v2] bug: further enhance use of CHECK_DATA_CORRUPTION
    On Tue, Apr 04, 2017 at 03:12:11PM -0700, Kees Cook wrote:
    > This continues in applying the CHECK_DATA_CORRUPTION tests where
    > appropriate, and pulling similar CONFIGs under the same check. Most
    > notably, this adds the checks to refcount_t so that system builders can
    > Oops their kernels when encountering a potential refcounter attack. (And
    > so now the LKDTM tests for refcount issues pass correctly.)
    >
    > The series depends on the changes in -next made to lib/refcount.c,
    > so it might be easiest if this goes through the locking tree...
    >
    > v2 is a rebase to -next and adjusts to using WARN_ONCE() instead of WARN().
    >
    > -Kees
    >
    > v1 was here: https://lkml.org/lkml/2017/3/6/720

    Ping? Just wondering what ever happened to this 3+ year old series...

    --
    Josh

    \
     
     \ /
      Last update: 2021-01-05 00:09    [W:2.461 / U:0.088 seconds]
    ©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site