From: Kees Cook <keescook@chromium.org>
To: Ganesh Goudar <ganeshgr@linux.ibm.com>
Cc: msuchanek@suse.de, linuxppc-dev@lists.ozlabs.org,
mahesh@linux.ibm.com, npiggin@gmail.com
Subject: Re: [PATCH v2 3/3] selftests/lkdtm: Enable selftest for SLB multihit
Date: Fri, 25 Sep 2020 12:59:42 -0700 [thread overview]
Message-ID: <202009251257.52EAF495@keescook> (raw)
In-Reply-To: <20200925103123.21102-4-ganeshgr@linux.ibm.com>
On Fri, Sep 25, 2020 at 04:01:23PM +0530, Ganesh Goudar wrote:
> Add PPC_SLB_MULTIHIT to lkdtm selftest framework.
>
> Signed-off-by: Ganesh Goudar <ganeshgr@linux.ibm.com>
> ---
> tools/testing/selftests/lkdtm/tests.txt | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/tools/testing/selftests/lkdtm/tests.txt b/tools/testing/selftests/lkdtm/tests.txt
> index 9d266e79c6a2..7eb3cf91c89e 100644
> --- a/tools/testing/selftests/lkdtm/tests.txt
> +++ b/tools/testing/selftests/lkdtm/tests.txt
> @@ -70,3 +70,4 @@ USERCOPY_KERNEL
> USERCOPY_KERNEL_DS
> STACKLEAK_ERASING OK: the rest of the thread stack is properly erased
> CFI_FORWARD_PROTO
> +PPC_SLB_MULTIHIT Recovered
Please squash this into the lkdtm patch -- I'd like test implementation
and kselftest awareness to go in together.
--
Kees Cook
next prev parent reply other threads:[~2020-09-25 20:01 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-25 10:31 [PATCH v2 0/3] powerpc/mce: Fix mce handler and add selftest Ganesh Goudar
2020-09-25 10:31 ` [PATCH v2 1/3] powerpc/mce: remove nmi_enter/exit from real mode handler Ganesh Goudar
2020-09-25 10:31 ` [PATCH v2 2/3] lkdtm/powerpc: Add SLB multihit test Ganesh Goudar
2020-09-25 14:04 ` kernel test robot
2020-09-25 19:57 ` Kees Cook
2020-09-28 17:32 ` Ganesh
2020-09-29 15:01 ` Michal Suchánek
2020-09-25 10:31 ` [PATCH v2 3/3] selftests/lkdtm: Enable selftest for SLB multihit Ganesh Goudar
2020-09-25 19:59 ` Kees Cook [this message]
2020-09-28 17:33 ` Ganesh
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=202009251257.52EAF495@keescook \
--to=keescook@chromium.org \
--cc=ganeshgr@linux.ibm.com \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mahesh@linux.ibm.com \
--cc=msuchanek@suse.de \
--cc=npiggin@gmail.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;
as well as URLs for NNTP newsgroup(s).