From: Shuah Khan <shuah@kernel.org>
To: Ingo Molnar <mingo@kernel.org>
Cc: Dave Hansen <dave.hansen@linux.intel.com>,
linux-kernel@vger.kernel.org, x86@kernel.org,
linux-kselftest@vger.kernel.org,
Shuah Khan <shuahkh@osg.samsung.com>,
Thomas Gleixner <tglx@linutronix.de>,
"H. Peter Anvin" <hpa@zytor.com>,
Shuah Khan <shuahkh@osg.samsung.com>
Subject: Re: [PATCH 2/2] selftests, x86, pkeys: test with random, unallocated protection keys
Date: Fri, 24 Feb 2017 07:41:48 -0700 [thread overview]
Message-ID: <16132b4a-0a04-a4d9-f081-3ef7d51e4d78@kernel.org> (raw)
In-Reply-To: <20170224074511.GB4095@gmail.com>
On 02/24/2017 12:45 AM, Ingo Molnar wrote:
>
> * Shuah Khan <shuah@kernel.org> wrote:
>
>> On 02/23/2017 03:26 PM, Dave Hansen wrote:
>>> Shuah, I assume you'll take this patch in through the selftests tree.
>>
>> Yes I can do that.
>
> No, let's not do that please, we have a fix and a self-tests update, I'd like them
> to be next in the Git space.
>
> I'll apply the testcase too when applying the pkeys fix, ok?
>
> Thanks,
>
> Ingo
>
>
Yup. I noticed the first patch has to go through x86 tree, Sounds good
to me. Please take both through. I am sending pull request for 4.11-rc1
today. I have a few pkeys patches in there. Hope there won't be any
conflicts.
thanks,
-- Shuah
next prev parent reply other threads:[~2017-02-24 14:51 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-23 22:26 [PATCH 1/2] x86, pkeys: check against max pkey to avoid overflows Dave Hansen
2017-02-23 22:26 ` [PATCH 2/2] selftests, x86, pkeys: test with random, unallocated protection keys Dave Hansen
2017-02-23 22:36 ` Shuah Khan
2017-02-24 7:45 ` Ingo Molnar
2017-02-24 14:41 ` Shuah Khan [this message]
2017-02-25 9:10 ` Ingo Molnar
2017-02-24 0:10 ` Kirill A. Shutemov
2017-02-24 0:07 ` [PATCH 1/2] x86, pkeys: check against max pkey to avoid overflows Kirill A. Shutemov
2017-03-01 9:57 ` [tip:x86/urgent] x86/pkeys: Check " tip-bot for 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=16132b4a-0a04-a4d9-f081-3ef7d51e4d78@kernel.org \
--to=shuah@kernel.org \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=shuahkh@osg.samsung.com \
--cc=tglx@linutronix.de \
--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®