Messages in this thread | | | Date | Wed, 24 Feb 2016 15:37:53 -0800 | Subject | Re: [PATCHv2] lkdtm: Add READ_AFTER_FREE test | From | Kees Cook <> |
| |
On Wed, Feb 24, 2016 at 1:48 PM, Kees Cook <keescook@chromium.org> wrote: > On Wed, Feb 24, 2016 at 11:40 AM, Laura Abbott <labbott@redhat.com> wrote: >> Yep, looks like the v1 patches and not the v2 patches which fix >> a known issue with the zeroing. > > Ah-ha, I'll go find those and retest.
I sent out a series that was rebased. It works for me, but I want to make sure I didn't make any glaring issues. I've also sent some fixes to the lkdtm tests. One thing that stands out to me still is that the READ_AFTER_FREE never shows poisoning. I remain confused, since obviously if zeroing is working, it's being correctly poisoned...
-Kees
-- Kees Cook Chrome OS & Brillo Security
| |