From: James Morse <james.morse@arm.com>
To: Kees Cook <keescook@chromium.org>
Cc: "kernel-hardening@lists.openwall.com"
<kernel-hardening@lists.openwall.com>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
Will Deacon <will.deacon@arm.com>,
Catalin Marinas <catalin.marinas@arm.com>,
Mark Rutland <mark.rutland@arm.com>,
Pratyush Anand <panand@redhat.com>,
keun-o.park@darkmatter.ae
Subject: [kernel-hardening] Re: [PATCH v4 0/3] arm64: usercopy: Implement stack frame object validation
Date: Thu, 30 Mar 2017 09:30:20 +0100 [thread overview]
Message-ID: <58DCC21C.6040705@arm.com> (raw)
In-Reply-To: <CAGXu5jKhVzH9OB6QgGb1u0sbnFGn5J72FnzNeGo076f52Scn+A@mail.gmail.com>
Hi Kees,
On 28/03/17 23:34, Kees Cook wrote:
> On Thu, Feb 16, 2017 at 4:54 PM, Kees Cook <keescook@chromium.org> wrote:
>> On Thu, Feb 16, 2017 at 10:29 AM, James Morse <james.morse@arm.com> wrote:
>>> This version of Sahara's arch_within_stack_frames() series replaces the
>>> open-coded stack walker with a call to arm64's existing walker.
> Is this still in progress? Seemed like it was very close?
Ah, sorry, I lost track of this when it jumped between mail folders... Sahara
had comments on the last patch.
How does all this fit with Al Viro's uaccess unification tree?:
https://lkml.org/lkml/2017/3/29/61
Thanks,
James
WARNING: multiple messages have this Message-ID (diff)
From: james.morse@arm.com (James Morse)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v4 0/3] arm64: usercopy: Implement stack frame object validation
Date: Thu, 30 Mar 2017 09:30:20 +0100 [thread overview]
Message-ID: <58DCC21C.6040705@arm.com> (raw)
In-Reply-To: <CAGXu5jKhVzH9OB6QgGb1u0sbnFGn5J72FnzNeGo076f52Scn+A@mail.gmail.com>
Hi Kees,
On 28/03/17 23:34, Kees Cook wrote:
> On Thu, Feb 16, 2017 at 4:54 PM, Kees Cook <keescook@chromium.org> wrote:
>> On Thu, Feb 16, 2017 at 10:29 AM, James Morse <james.morse@arm.com> wrote:
>>> This version of Sahara's arch_within_stack_frames() series replaces the
>>> open-coded stack walker with a call to arm64's existing walker.
> Is this still in progress? Seemed like it was very close?
Ah, sorry, I lost track of this when it jumped between mail folders... Sahara
had comments on the last patch.
How does all this fit with Al Viro's uaccess unification tree?:
https://lkml.org/lkml/2017/3/29/61
Thanks,
James
next prev parent reply other threads:[~2017-03-30 8:30 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-16 18:29 [kernel-hardening] [PATCH v4 0/3] arm64: usercopy: Implement stack frame object validation James Morse
2017-02-16 18:29 ` James Morse
2017-02-16 18:29 ` [kernel-hardening] [PATCH v4 1/3] usercopy: create enum stack_type James Morse
2017-02-16 18:29 ` James Morse
2017-04-04 22:19 ` [kernel-hardening] " Kees Cook
2017-04-04 22:19 ` Kees Cook
2017-02-16 18:29 ` [kernel-hardening] [PATCH v4 2/3] arm64: Add arch_within_stack_frames() for hardened usercopy James Morse
2017-02-16 18:29 ` James Morse
2017-02-17 0:47 ` [kernel-hardening] " Kees Cook
2017-02-17 0:47 ` Kees Cook
2017-02-16 18:29 ` [kernel-hardening] [PATCH v4 3/3] arm64/uaccess: Add hardened usercopy check for bad stack accesses James Morse
2017-02-16 18:29 ` James Morse
2017-02-17 0:44 ` [kernel-hardening] " Kees Cook
2017-02-17 0:44 ` Kees Cook
2017-02-17 18:09 ` [kernel-hardening] " Keun-O Park
2017-02-17 18:09 ` Keun-O Park
2017-03-30 8:32 ` James Morse
2017-03-30 8:32 ` James Morse
2017-02-17 0:54 ` [kernel-hardening] Re: [PATCH v4 0/3] arm64: usercopy: Implement stack frame object validation Kees Cook
2017-02-17 0:54 ` Kees Cook
2017-03-28 22:34 ` [kernel-hardening] " Kees Cook
2017-03-28 22:34 ` Kees Cook
2017-03-30 8:30 ` James Morse [this message]
2017-03-30 8:30 ` James Morse
2017-03-30 19:54 ` [kernel-hardening] " Kees Cook
2017-03-30 19:54 ` 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=58DCC21C.6040705@arm.com \
--to=james.morse@arm.com \
--cc=catalin.marinas@arm.com \
--cc=keescook@chromium.org \
--cc=kernel-hardening@lists.openwall.com \
--cc=keun-o.park@darkmatter.ae \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=mark.rutland@arm.com \
--cc=panand@redhat.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 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.