From: Shuah Khan <shuahkh@osg.samsung.com>
To: Dave Hansen <dave.hansen@linux.intel.com>, linux-kernel@vger.kernel.org
Cc: x86@kernel.org, Shuah Khan <shuahkh@osg.samsung.com>
Subject: Re: [PATCH 2/4] selftests, x86, protection_keys: remove dead code
Date: Thu, 2 Feb 2017 16:36:41 -0700 [thread overview]
Message-ID: <c5ceeb4b-273a-a69b-cd82-ce4cc075b925@osg.samsung.com> (raw)
In-Reply-To: <20170202232845.83211A3D@viggo.jf.intel.com>
On 02/02/2017 04:28 PM, Dave Hansen wrote:
> From: Shuah Khan <shuahkh@osg.samsung.com>
>
> Remove commented out calls to pkey_get().
>
> Signed-off-by: Shuah Khan <shuahkh@osg.samsung.com>
> Signed-off-by: Dave Hansen <dave.hansen@linux.intel.com>
Hi Dave,
This patches is already in linux-kselftest next for 4.11
Is there a reason why you chose to resend these.
-- Shuah
> ---
>
> b/tools/testing/selftests/x86/protection_keys.c | 10 ----------
> 1 file changed, 10 deletions(-)
>
> diff -puN tools/testing/selftests/x86/protection_keys.c~selftests-x86-protection-keys-remove-dead-code tools/testing/selftests/x86/protection_keys.c
> --- a/tools/testing/selftests/x86/protection_keys.c~selftests-x86-protection-keys-remove-dead-code 2017-02-02 15:27:13.329130196 -0800
> +++ b/tools/testing/selftests/x86/protection_keys.c 2017-02-02 15:27:13.333130376 -0800
> @@ -1114,11 +1114,6 @@ void test_pkey_syscalls_on_non_allocated
> err = sys_pkey_free(i);
> pkey_assert(err);
>
> - /* not enforced when pkey_get() is not a syscall
> - err = pkey_get(i, 0);
> - pkey_assert(err < 0);
> - */
> -
> err = sys_pkey_free(i);
> pkey_assert(err);
>
> @@ -1133,11 +1128,6 @@ void test_pkey_syscalls_bad_args(int *pt
> int err;
> int bad_pkey = NR_PKEYS+99;
>
> - /* not enforced when pkey_get() is not a syscall
> - err = pkey_get(bad_pkey, bad_flag);
> - pkey_assert(err < 0);
> - */
> -
> /* pass a known-invalid pkey in: */
> err = sys_mprotect_pkey(ptr, PAGE_SIZE, PROT_READ, bad_pkey);
> pkey_assert(err);
> _
>
next prev parent reply other threads:[~2017-02-02 23:36 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-02 23:28 [PATCH 0/4] selftests, x86: updates for x86 protection keys self tests Dave Hansen
2017-02-02 23:28 ` [PATCH 1/4] selftests, x86, protection_keys: fix unused variable compile warnings Dave Hansen
2017-02-02 23:36 ` Shuah Khan
2017-02-02 23:45 ` Dave Hansen
2017-02-02 23:49 ` Shuah Khan
2017-02-03 6:43 ` Ingo Molnar
2017-02-02 23:28 ` [PATCH 2/4] selftests, x86, protection_keys: remove dead code Dave Hansen
2017-02-02 23:36 ` Shuah Khan [this message]
2017-02-02 23:28 ` [PATCH 3/4] selftests, x86, protection_keys: fix uninitialized variable warning Dave Hansen
2017-02-02 23:28 ` [PATCH 4/4] selftests, x86, protection_keys: fix wrong offset in siginfo Dave Hansen
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=c5ceeb4b-273a-a69b-cd82-ce4cc075b925@osg.samsung.com \
--to=shuahkh@osg.samsung.com \
--cc=dave.hansen@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=x86@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®