Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAGXu5jKH3E3w6D70gfrZiCcXW04Bc-i+kU-HDVJLXkoJaS7RkQ@mail.gmail.com>
Date: Thu, 22 Feb 2018 15:43:55 -0800
From: Kees Cook <keescook@...omium.org>
To: Laura Abbott <labbott@...hat.com>
Cc: Alexander Popov <alex.popov@...ux.com>, 
	Kernel Hardening <kernel-hardening@...ts.openwall.com>
Subject: Re: [PATCH 0/2] Update stackleak for gcc-8

On Thu, Feb 22, 2018 at 3:14 PM, Laura Abbott <labbott@...hat.com> wrote:
>
> Okay I _think_ this should be the solution for gcc-8. I've split this
> into two patches, one for the generic framework and the other for the
> stackleak plugin itself.

Nice! Thanks for solving this!

> Kees, I'll let you figure out how to apply
> these. Feel free to fold in as appropriate.

Other than the suggestion to have fewer ifdef in stackleak, this looks
fine. Alexander, feel free to take these both (with adjustments) for
the stackleak series: stackleak is the only user of
cgraph_create_edge() so I think it's fine to adjust gcc-common.h in
the series.

-Kees

-- 
Kees Cook
Pixel Security

Powered by blists - more mailing lists

Confused about mailing lists and their use? Read about mailing lists on Wikipedia and check out these guidelines on proper formatting of your messages.