From: Greg Hackmann <ghackmann@google.com>
To: Greg KH <gregkh@linuxfoundation.org>,
Jean-Baptiste Theou <jb@essential.com>,
Sami Tolvanen <samitolvanen@google.com>
Cc: Ard Biesheuvel <ard.biesheuvel@linaro.org>,
Mark Rutland <mark.rutland@arm.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Will Deacon <will.deacon@arm.com>, Dan Rue <dan.rue@linaro.org>,
Mark Brown <mark.brown@linaro.org>,
Marc Zyngier <marc.zyngier@arm.com>
Subject: Re: Linux 4.9.93
Date: Mon, 9 Apr 2018 10:02:17 -0700 [thread overview]
Message-ID: <fbd6de8b-d2ab-9fcd-75b6-7151f24309e9@google.com> (raw)
In-Reply-To: <20180409114146.GA20636@kroah.com>
On 04/09/2018 04:41 AM, Greg KH wrote:
> On Mon, Apr 09, 2018 at 06:57:51PM +0900, Jean-Baptiste Theou wrote:
>> On Mon, 9 Apr 2018 11:49:37 +0200
>> Ard Biesheuvel <ard.biesheuvel@linaro.org> wrote:
>>
>>> On 9 April 2018 at 11:30, Greg KH <gregkh@linuxfoundation.org> wrote:
>>>> On Mon, Apr 09, 2018 at 06:05:34PM +0900, Jean-Baptiste Theou wrote:
>>>>> Hi,
>>>>>
>>>>> After this patchset, a kernel built with CFI fails. Disabling
>>>>> UNMAP_KERNEL_AT_EL0 fix the issue obviously.
>>>
>>> How does one 'build a kernel with CFI' for arm64?
>>
>> From Google work on Android-4.9
>>
>> https://android.googlesource.com/kernel/common/+/00a195e7c0752ff5d65c9caadfbcc226270ca232
>>
>> I am not sure what is the plan on their side to upstream (Greg?), but definitely
>> useful to isolate actual issues.
>
> Ah, yeah, if you are taking anything from the Android tree, all bets are
> off :)
>
> Greg Hackmann can probably answer the questions about CFI and these
> patches, as he's working on merging this stable release into the
> android-4.9 branch this week. I'll let him deal with this...
>
> thanks,
>
> greg k-h
>
I've added Sami Tolvanen, who's handling CFI in the kernel.
Sami, what are the plans for upstreaming this work?
next prev parent reply other threads:[~2018-04-09 17:02 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-09 9:05 Jean-Baptiste Theou
2018-04-09 9:30 ` Greg KH
2018-04-09 9:44 ` Marc Zyngier
2018-04-09 9:49 ` Ard Biesheuvel
2018-04-09 9:57 ` Jean-Baptiste Theou
2018-04-09 10:07 ` Mark Rutland
2018-04-09 10:41 ` Jean-Baptiste Theou
2018-04-09 10:25 ` Ard Biesheuvel
2018-04-09 10:28 ` Jean-Baptiste Theou
2018-04-09 11:41 ` Greg KH
2018-04-09 17:02 ` Greg Hackmann [this message]
2018-04-09 20:32 ` Sami Tolvanen
2018-04-09 9:55 ` Mark Rutland
-- strict thread matches above, loose matches on Subject: below --
2018-04-08 15:08 Greg KH
2018-04-08 15:08 ` Greg KH
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=fbd6de8b-d2ab-9fcd-75b6-7151f24309e9@google.com \
--to=ghackmann@google.com \
--cc=ard.biesheuvel@linaro.org \
--cc=dan.rue@linaro.org \
--cc=gregkh@linuxfoundation.org \
--cc=jb@essential.com \
--cc=linux-kernel@vger.kernel.org \
--cc=marc.zyngier@arm.com \
--cc=mark.brown@linaro.org \
--cc=mark.rutland@arm.com \
--cc=samitolvanen@google.com \
--cc=will.deacon@arm.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
Powered by JetHome