From: Kees Cook <keescook@chromium.org>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Prasad Sodagudi <psodagud@codeaurora.org>,
Sami Tolvanen <samitolvanen@google.com>,
Amit Daniel Kachhap <amit.kachhap@arm.com>,
linux-kselftest@vger.kernel.org,
clang-built-linux@googlegroups.com, linux-kernel@vger.kernel.org,
richard -rw- weinberger <richard.weinberger@gmail.com>
Subject: Re: [PATCH drivers/misc 0/4] lkdtm: Various clean ups
Date: Tue, 23 Jun 2020 17:01:39 -0700 [thread overview]
Message-ID: <202006231701.DACC6F2C9@keescook> (raw)
In-Reply-To: <2356a78c-750b-538f-3d64-b9c78aff89cb@infradead.org>
On Tue, Jun 23, 2020 at 04:32:12PM -0700, Randy Dunlap wrote:
> On 6/23/20 4:10 PM, Kees Cook wrote:
> > On Fri, May 29, 2020 at 01:03:43PM -0700, Kees Cook wrote:
> >> Hi Greg,
> >>
> >> Can you please apply these patches to your drivers/misc tree for LKDTM?
> >> It's mostly a collection of fixes and improvements and tweaks to the
> >> selftest integration.
> >
> > Friendly ping -- we're past -rc2 now. :)
> >
> > Thanks!
> >
> > -Kees
> >
> >>
> >> Thanks!
> >>
> >> -Kees
> >>
> >> Kees Cook (4):
> >> lkdtm: Avoid more compiler optimizations for bad writes
> >> lkdtm/heap: Avoid edge and middle of slabs
> >> selftests/lkdtm: Reset WARN_ONCE to avoid false negatives
> >> lkdtm: Make arch-specific tests always available
> >>
> >> drivers/misc/lkdtm/bugs.c | 45 +++++++++++++------------
> >> drivers/misc/lkdtm/heap.c | 9 ++---
> >> drivers/misc/lkdtm/lkdtm.h | 2 --
> >> drivers/misc/lkdtm/perms.c | 22 ++++++++----
> >> drivers/misc/lkdtm/usercopy.c | 7 ++--
> >> tools/testing/selftests/lkdtm/run.sh | 6 ++++
> >> tools/testing/selftests/lkdtm/tests.txt | 1 +
> >> 7 files changed, 56 insertions(+), 36 deletions(-)
> >>
> >> --
> >> 2.25.1
> >>
> >
>
> >> Regardless, it seems arch/x86/um/asm/desc.h is not needed any more?
>
> > True that, we can rip the file.
>
> Has anyone fixed the uml build errors?
Oh, I thought that had nothing to do with the lkdtm changes? Should I
rip out that file and resend?
--
Kees Cook
next prev parent reply other threads:[~2020-06-24 0:01 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-29 20:03 [PATCH drivers/misc 0/4] lkdtm: Various clean ups Kees Cook
2020-05-29 20:03 ` [PATCH 1/4] lkdtm: Avoid more compiler optimizations for bad writes Kees Cook
2020-05-29 20:10 ` Nick Desaulniers
2020-05-29 20:03 ` [PATCH 2/4] lkdtm/heap: Avoid edge and middle of slabs Kees Cook
2020-05-29 20:03 ` [PATCH 3/4] selftests/lkdtm: Reset WARN_ONCE to avoid false negatives Kees Cook
2020-05-29 20:22 ` Shuah Khan
2020-05-29 20:03 ` [PATCH 4/4] lkdtm: Make arch-specific tests always available Kees Cook
2020-06-23 23:10 ` [PATCH drivers/misc 0/4] lkdtm: Various clean ups Kees Cook
2020-06-23 23:32 ` Randy Dunlap
2020-06-24 0:01 ` Kees Cook [this message]
2020-06-24 7:23 ` Richard Weinberger
2020-06-24 20:36 ` Kees Cook
2020-06-24 21:29 ` Randy Dunlap
2020-06-24 22:01 ` Richard Weinberger
2020-06-24 22:23 ` Randy Dunlap
2020-06-24 22:35 ` Randy Dunlap
2020-06-25 1:45 ` Randy Dunlap
2020-06-25 6:06 ` Kees Cook
2020-06-25 6:24 ` Richard Weinberger
2020-06-25 15:24 ` Randy Dunlap
2020-06-24 6:13 ` Greg Kroah-Hartman
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=202006231701.DACC6F2C9@keescook \
--to=keescook@chromium.org \
--cc=amit.kachhap@arm.com \
--cc=clang-built-linux@googlegroups.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=psodagud@codeaurora.org \
--cc=rdunlap@infradead.org \
--cc=richard.weinberger@gmail.com \
--cc=samitolvanen@google.com \
/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