[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20151108083708.GB1900@x>
Date: Sun, 8 Nov 2015 00:37:09 -0800
From: Josh Triplett <josh@...htriplett.org>
To: Emese Revfy <re.emese@...il.com>
Cc: Kees Cook <keescook@...omium.org>,
"kernel-hardening@...ts.openwall.com" <kernel-hardening@...ts.openwall.com>,
PaX Team <pageexec@...email.hu>,
Brad Spengler <spender@...ecurity.net>,
Greg KH <gregkh@...uxfoundation.org>,
Theodore Tso <tytso@...gle.com>
Subject: Re: Proposal for kernel self protection features
On Sat, Nov 07, 2015 at 10:42:35PM +0100, Emese Revfy wrote:
> On Fri, 6 Nov 2015 16:25:08 -0800
> Josh Triplett <josh@...htriplett.org> wrote:
>
> > On Fri, Nov 06, 2015 at 03:30:39PM -0800, Kees Cook wrote:
> > > On Fri, Nov 6, 2015 at 2:55 PM, Emese Revfy <re.emese@...il.com> wrote:
> > > > * initify: This plugin isn't security related either.
> > > > It moves string constants (__func__ and function string arguments
> > > > marked by the nocapture attribute) only referenced in
> > > > __init/__exit functions to __initconst/__exitconst sections.
> > > > It reduces memory usage (many kB), I think it may be important for
> > > > embedded systems.
> > >
> > > I bet the Tinification project ( https://tiny.wiki.kernel.org/ ) would
> > > be interested in this! (CCing Josh for thoughts.)
> >
> > I'd be quite interested.
> >
> > Could the plugin operate in a mode where it emits warnings to add such
> > annotations explicitly in the code, rather than just automatically
> > moving the data?
>
> I can do it, but as Ard said it also moves e.g., format strings and __func__
> that is not possible to do with source code changes.
Ah. It'd be nice to have GCC options in default GCC to move those.
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.
