From: Catalin Marinas <catalin.marinas@arm.com>
To: Kees Cook <keescook@chromium.org>
Cc: Mark Rutland <mark.rutland@arm.com>,
Ard Biesheuvel <ard.biesheuvel@linaro.org>,
"kernel-hardening@lists.openwall.com"
<kernel-hardening@lists.openwall.com>,
Will Deacon <will.deacon@arm.com>,
AKASHI Takahiro <takahiro.akashi@linaro.org>,
James Morse <james.morse@arm.com>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Subject: [kernel-hardening] Re: [PATCH v3 0/7] arm64: Privileged Access Never using TTBR0_EL1 switching
Date: Sat, 15 Oct 2016 15:35:49 +0100 [thread overview]
Message-ID: <20161015143548.GA31114@MBP.local> (raw)
In-Reply-To: <CAGXu5jKMZTo7m=ygm7x8w__1my0jiQiVAiv9NowQ8pfQqCnjmw@mail.gmail.com>
Hi Kees,
On Fri, Oct 14, 2016 at 02:44:33PM -0700, Kees Cook wrote:
> Just checking in on this feature -- I don't see it in -next nor
> already in the tree. Is there any chance this is going to make the
> v4.9 merge window?
As I said in the cover letter, I'll rebase it on top of 4.9-rc1 as there
are some clean-ups that this series would conflict with. So I am
targeting 4.10 with this patch series.
> It didn't sound like there were any unresolved issues remaining?
There are a few issues spotted by Mark which I'll address in the next
version, but nothing major.
--
Catalin
WARNING: multiple messages have this Message-ID (diff)
From: catalin.marinas@arm.com (Catalin Marinas)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v3 0/7] arm64: Privileged Access Never using TTBR0_EL1 switching
Date: Sat, 15 Oct 2016 15:35:49 +0100 [thread overview]
Message-ID: <20161015143548.GA31114@MBP.local> (raw)
In-Reply-To: <CAGXu5jKMZTo7m=ygm7x8w__1my0jiQiVAiv9NowQ8pfQqCnjmw@mail.gmail.com>
Hi Kees,
On Fri, Oct 14, 2016 at 02:44:33PM -0700, Kees Cook wrote:
> Just checking in on this feature -- I don't see it in -next nor
> already in the tree. Is there any chance this is going to make the
> v4.9 merge window?
As I said in the cover letter, I'll rebase it on top of 4.9-rc1 as there
are some clean-ups that this series would conflict with. So I am
targeting 4.10 with this patch series.
> It didn't sound like there were any unresolved issues remaining?
There are a few issues spotted by Mark which I'll address in the next
version, but nothing major.
--
Catalin
next prev parent reply other threads:[~2016-10-15 14:35 UTC|newest]
Thread overview: 64+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-13 17:46 [kernel-hardening] [PATCH v3 0/7] arm64: Privileged Access Never using TTBR0_EL1 switching Catalin Marinas
2016-09-13 17:46 ` Catalin Marinas
2016-09-13 17:46 ` [kernel-hardening] [PATCH v3 1/7] arm64: Factor out PAN enabling/disabling into separate uaccess_* macros Catalin Marinas
2016-09-13 17:46 ` Catalin Marinas
2016-09-15 15:10 ` [kernel-hardening] " Mark Rutland
2016-09-15 15:10 ` Mark Rutland
2016-09-13 17:46 ` [kernel-hardening] [PATCH v3 2/7] arm64: Factor out TTBR0_EL1 post-update workaround into a specific asm macro Catalin Marinas
2016-09-13 17:46 ` Catalin Marinas
2016-09-15 15:19 ` [kernel-hardening] " Mark Rutland
2016-09-15 15:19 ` Mark Rutland
2016-09-13 17:46 ` [kernel-hardening] [PATCH v3 3/7] arm64: Introduce uaccess_{disable,enable} functionality based on TTBR0_EL1 Catalin Marinas
2016-09-13 17:46 ` [PATCH v3 3/7] arm64: Introduce uaccess_{disable, enable} " Catalin Marinas
2016-09-13 20:45 ` [kernel-hardening] Re: [PATCH v3 3/7] arm64: Introduce uaccess_{disable,enable} " Kees Cook
2016-09-13 20:45 ` Kees Cook
2016-09-14 8:52 ` [kernel-hardening] " Mark Rutland
2016-09-14 8:52 ` Mark Rutland
2016-09-14 16:27 ` [kernel-hardening] " Kees Cook
2016-09-14 16:27 ` Kees Cook
2016-09-13 17:46 ` [kernel-hardening] [PATCH v3 4/7] arm64: Disable TTBR0_EL1 during normal kernel execution Catalin Marinas
2016-09-13 17:46 ` Catalin Marinas
2016-09-14 16:45 ` [kernel-hardening] " Will Deacon
2016-09-14 16:45 ` Will Deacon
2016-09-13 17:46 ` [kernel-hardening] [PATCH v3 5/7] arm64: Handle faults caused by inadvertent user access with PAN enabled Catalin Marinas
2016-09-13 17:46 ` Catalin Marinas
2016-09-16 11:33 ` [kernel-hardening] " Mark Rutland
2016-09-16 11:33 ` Mark Rutland
2016-09-16 15:55 ` [kernel-hardening] " Catalin Marinas
2016-09-16 15:55 ` Catalin Marinas
2016-09-13 17:46 ` [kernel-hardening] [PATCH v3 6/7] arm64: xen: Enable user access before a privcmd hvc call Catalin Marinas
2016-09-13 17:46 ` Catalin Marinas
2016-09-13 17:46 ` [kernel-hardening] [PATCH v3 7/7] arm64: Enable CONFIG_ARM64_SW_TTBR0_PAN Catalin Marinas
2016-09-13 17:46 ` Catalin Marinas
2016-09-14 10:13 ` [kernel-hardening] Re: [PATCH v3 0/7] arm64: Privileged Access Never using TTBR0_EL1 switching Ard Biesheuvel
2016-09-14 10:13 ` Ard Biesheuvel
2016-09-14 10:27 ` [kernel-hardening] " Mark Rutland
2016-09-14 10:27 ` Mark Rutland
2016-09-14 10:30 ` [kernel-hardening] " Ard Biesheuvel
2016-09-14 10:30 ` Ard Biesheuvel
2016-09-14 10:36 ` [kernel-hardening] " Mark Rutland
2016-09-14 10:36 ` Mark Rutland
2016-09-14 10:48 ` [kernel-hardening] " Mark Rutland
2016-09-14 10:48 ` Mark Rutland
2016-09-14 20:54 ` [kernel-hardening] " David Brown
2016-09-14 20:54 ` David Brown
2016-09-15 9:52 ` Catalin Marinas
2016-09-15 9:52 ` Catalin Marinas
2016-09-15 16:20 ` [kernel-hardening] " Mark Rutland
2016-09-15 16:20 ` Mark Rutland
2016-09-15 16:41 ` [kernel-hardening] " Mark Rutland
2016-09-15 16:41 ` Mark Rutland
2016-09-29 22:44 ` [kernel-hardening] " Sami Tolvanen
2016-09-29 22:44 ` Sami Tolvanen
2016-09-30 18:42 ` Kees Cook
2016-09-30 18:42 ` Kees Cook
2016-10-27 14:54 ` Catalin Marinas
2016-10-27 14:54 ` Catalin Marinas
2016-10-27 21:23 ` Kees Cook
2016-10-27 21:23 ` Kees Cook
2016-10-14 21:44 ` Kees Cook
2016-10-14 21:44 ` Kees Cook
2016-10-15 14:35 ` Catalin Marinas [this message]
2016-10-15 14:35 ` Catalin Marinas
2016-10-16 2:04 ` [kernel-hardening] " Kees Cook
2016-10-16 2:04 ` Kees Cook
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=20161015143548.GA31114@MBP.local \
--to=catalin.marinas@arm.com \
--cc=ard.biesheuvel@linaro.org \
--cc=james.morse@arm.com \
--cc=keescook@chromium.org \
--cc=kernel-hardening@lists.openwall.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=mark.rutland@arm.com \
--cc=takahiro.akashi@linaro.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.