From: Quentin Casasnovas <quentin.casasnovas@oracle.com>
To: Kees Cook <keescook@chromium.org>
Cc: Quentin Casasnovas <quentin.casasnovas@oracle.com>,
"kernel-hardening@lists.openwall.com"
<kernel-hardening@lists.openwall.com>
Subject: [kernel-hardening] Re: status: GRKERNSEC_KSTACKOVERFLOW
Date: Fri, 22 Jan 2016 23:04:35 +0100 [thread overview]
Message-ID: <20160122220435.GD5130@chrystal.uk.oracle.com> (raw)
In-Reply-To: <CAGXu5jLP4mfyeSoiMzTyGiRnx26Xp+US2djvY9MP0cDoBa2TBQ@mail.gmail.com>
On Tue, Jan 19, 2016 at 04:03:12PM -0800, Kees Cook wrote:
> On Fri, Nov 27, 2015 at 12:23 PM, Kees Cook <keescook@chromium.org> wrote:
> > On Wed, Nov 25, 2015 at 3:45 PM, Quentin Casasnovas
> > <quentin.casasnovas@oracle.com> wrote:
> >> On Tue, Nov 24, 2015 at 11:10:09AM -0800, Kees Cook wrote:
> >>> Hi,
> >>>
> >>
> >> Hi Kees,
> >>
> >>> I just wanted to check in and see how progress was going on the stack
> >>> overflow feature. Anything we can help with?
> >>>
> >>
> >> Sorry for not following up on this, I've been busy and haven't had the time
> >> to finish it properly. I've pushed an initial WIP break up of the
> >> KSTACK_OVERFLOW feature on my github:
> >>
> >> https://github.com/casasnovas/linux/tree/quentin-split-kstackoverflow
> >
> > Great! Thanks for the update!
>
> Hi Quentin,
>
> Has anything moved on KSTACK_OVERFLOW? I'd love to start getting some
> code tested if it's ready.
>
Hi Kees,
Sorry I've been very bad at finding free time recenlty, being a new dad
takes more time than expected :)
I've got next week off so hopefully I can spend some time on this, starting
with moving the thread_info off the stack and then splitting properly the
rest of the KSTACK_OVERFLOW.
Quentin
next prev parent reply other threads:[~2016-01-22 22:04 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-24 19:10 [kernel-hardening] status: GRKERNSEC_KSTACKOVERFLOW Kees Cook
2015-11-25 23:45 ` [kernel-hardening] " Quentin Casasnovas
2015-11-26 16:39 ` Quentin Casasnovas
2015-11-27 20:09 ` Kees Cook
2015-11-28 9:19 ` Quentin Casasnovas
2015-11-30 20:12 ` Kees Cook
2015-11-26 17:17 ` Quentin Casasnovas
2015-11-27 20:18 ` Kees Cook
2015-11-28 9:16 ` Quentin Casasnovas
2015-11-27 20:23 ` Kees Cook
2015-11-28 9:25 ` Quentin Casasnovas
2016-01-20 0:03 ` Kees Cook
2016-01-22 22:04 ` Quentin Casasnovas [this message]
2016-04-21 20:31 ` Kees Cook
2016-04-27 8:30 ` Quentin Casasnovas
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=20160122220435.GD5130@chrystal.uk.oracle.com \
--to=quentin.casasnovas@oracle.com \
--cc=keescook@chromium.org \
--cc=kernel-hardening@lists.openwall.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.