From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Kees Cook <keescook@chromium.org>
Cc: Arnd Bergmann <arnd@arndb.de>,
Laura Abbott <labbott@fedoraproject.org>,
LKML <linux-kernel@vger.kernel.org>,
"kernel-hardening@lists.openwall.com"
<kernel-hardening@lists.openwall.com>
Subject: Re: [PATCHv2 0/3] LKDTM use after free test updates
Date: Fri, 26 Feb 2016 22:57:07 +0000 [thread overview]
Message-ID: <20160226225706.GA11672@kroah.com> (raw)
In-Reply-To: <CAGXu5jKgOwPivXh=eWpX4zuEVd6MfEtJNbh7nwRjitnfNP7_Sw@mail.gmail.com>
On Fri, Feb 26, 2016 at 01:39:14PM -0800, Kees Cook wrote:
> On Thu, Feb 25, 2016 at 4:36 PM, Laura Abbott <labbott@fedoraproject.org> wrote:
> > Hi,
> >
> > This is v2 of the LKDTM test update. This is mostly taking the updates
> > Kees gave for the previous series and bringing it in.
> >
> > Laura Abbott (3):
> > lkdtm: Add READ_AFTER_FREE test
> > lkdtm: Update WRITE_AFTER_FREE test
> > lkdtm: Add read/write after free tests for buddy memory
> >
> > drivers/misc/lkdtm.c | 98 ++++++++++++++++++++++++++++++++++++++++++++++++++--
> > 1 file changed, 95 insertions(+), 3 deletions(-)
>
> Thanks!
>
> Please consider the series:
>
> Acked-by: Kees Cook <keescook@chromium.org>
>
> And, say, while we're at it... Greg, would you mind if I became the
> lkdtm maintainer?
Not at all, I was treating you as one anyway, waiting till I got acks
from you before committing anything :)
Feel free to send a patch to MAINTAINERS for me to add for this.
thanks,
greg k-h
next prev parent reply other threads:[~2016-02-26 23:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-26 0:36 Laura Abbott
2016-02-26 0:36 ` [PATCHv4 1/3] lkdtm: Add READ_AFTER_FREE test Laura Abbott
2016-02-26 0:36 ` [PATCH 2/3] lkdtm: Update WRITE_AFTER_FREE test Laura Abbott
2016-02-26 0:36 ` [PATCHv2 3/3] lkdtm: Add read/write after free tests for buddy memory Laura Abbott
2016-02-26 21:39 ` [PATCHv2 0/3] LKDTM use after free test updates Kees Cook
2016-02-26 22:57 ` Greg Kroah-Hartman [this message]
2016-02-26 22:57 ` Kees Cook
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20160226225706.GA11672@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=arnd@arndb.de \
--cc=keescook@chromium.org \
--cc=kernel-hardening@lists.openwall.com \
--cc=labbott@fedoraproject.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®