From: Kees Cook <keescook@chromium.org>
To: Keun-O Park <kpark3469@gmail.com>
Cc: Will Deacon <will.deacon@arm.com>,
Kernel Hardening <kernel-hardening@lists.openwall.com>,
James Morse <james.morse@arm.com>,
Catalin Marinas <catalin.marinas@arm.com>,
Mark Rutland <mark.rutland@arm.com>,
keun-o.park@darkmatter.ae
Subject: Re: [PATCH 0/4] usercopy: reimplement arch_within_stack_frames
Date: Wed, 4 Apr 2018 15:46:36 -0700 [thread overview]
Message-ID: <CAGXu5j+D_s6qha959dCQ3ViMuXzvOwFiw=9Bsh_=wT_7maqEKQ@mail.gmail.com> (raw)
In-Reply-To: <CA+KhAHbv4CbuWcKt7Sbn8g_BcMCSFaJTmHtJedDESHqHc1mmGQ@mail.gmail.com>
On Wed, Mar 28, 2018 at 3:16 AM, Keun-O Park <kpark3469@gmail.com> wrote:
> Hi Will,
>
> On Mon, Mar 26, 2018 at 4:35 PM, Will Deacon <will.deacon@arm.com> wrote:
>> Hi Sahara,
>>
>> On Thu, Mar 01, 2018 at 02:19:47PM +0400, kpark3469@gmail.com wrote:
>>> From: Sahara <keun-o.park@darkmatter.ae>
>>>
>>> This series of patches introduce the arm64 arch_within_stack_frames
>>> implementation using stacktrace functions. Also the base code is
>>> moved from thread_info.h to stacktrace.h. x86 code is reimplemented
>>> to use frame pointer unwinder functions.
>>
>> What's the status on this series? I'm ok taking the arm64 patch from James
>> to bring us up to speed with x86, but it doesn't make sense without the
>> first patch in the series because the arch callback is out-of-line.
>>
>> Will
>
> I haven't received any response from Kees or other engineers about
> this series of patches yet.
> Hi Kees, any comment on these patches to put these on the next stage?
Hi! Sorry for the delay, I'll send some notes now...
-Kees
--
Kees Cook
Pixel Security
prev parent reply other threads:[~2018-04-04 22:46 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-01 10:19 [PATCH 0/4] usercopy: reimplement arch_within_stack_frames kpark3469
2018-03-01 10:19 ` [PATCH 1/4] stacktrace: move arch_within_stack_frames from thread_info.h kpark3469
2018-03-01 10:19 ` [PATCH 2/4] arm64: usercopy: implement arch_within_stack_frames kpark3469
2018-03-01 10:19 ` [PATCH 3/4] arm64: usercopy: consider dynamic array stack variable kpark3469
2018-03-01 10:19 ` [PATCH 4/4] x86: usercopy: reimplement arch_within_stack_frames with unwinder kpark3469
2018-04-04 23:10 ` Kees Cook
2018-04-04 23:11 ` Kees Cook
2018-04-09 5:40 ` Keun-O Park
2018-04-04 22:57 ` [PATCH 3/4] arm64: usercopy: consider dynamic array stack variable Kees Cook
2018-04-08 6:45 ` Keun-O Park
2018-04-09 5:54 ` Keun-O Park
2018-04-04 22:55 ` [PATCH 2/4] arm64: usercopy: implement arch_within_stack_frames Kees Cook
2018-04-08 6:39 ` Keun-O Park
2018-04-04 22:52 ` [PATCH 1/4] stacktrace: move arch_within_stack_frames from thread_info.h Kees Cook
2018-03-26 14:35 ` [PATCH 0/4] usercopy: reimplement arch_within_stack_frames Will Deacon
2018-03-28 10:16 ` Keun-O Park
2018-04-04 22:46 ` Kees Cook [this message]
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='CAGXu5j+D_s6qha959dCQ3ViMuXzvOwFiw=9Bsh_=wT_7maqEKQ@mail.gmail.com' \
--to=keescook@chromium.org \
--cc=catalin.marinas@arm.com \
--cc=james.morse@arm.com \
--cc=kernel-hardening@lists.openwall.com \
--cc=keun-o.park@darkmatter.ae \
--cc=kpark3469@gmail.com \
--cc=mark.rutland@arm.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.