From: Joe Perches <joe@perches.com>
To: Emese Revfy <re.emese@gmail.com>,
kernel-hardening@lists.openwall.com,
Mathias Krause <minipli@googlemail.com>
Cc: pageexec@freemail.hu, spender@grsecurity.net, mmarek@suse.com,
keescook@chromium.org, linux-kernel@vger.kernel.org,
yamada.masahiro@socionext.com, linux-kbuild@vger.kernel.org,
minipli@ld-linux.so, linux@armlinux.org.uk,
catalin.marinas@arm.com, linux@rasmusvillemoes.dk,
david.brown@linaro.org, benh@kernel.crashing.org,
tglx@linutronix.de, akpm@linux-foundation.org,
jlayton@poochiereds.net, arnd@arndb.de
Subject: Re: [PATCH v1 0/2] Introduce the initify gcc plugin
Date: Tue, 28 Jun 2016 11:48:54 -0700 [thread overview]
Message-ID: <1467139734.24287.45.camel@perches.com> (raw)
In-Reply-To: <1467131708.24287.29.camel@perches.com>
On Tue, 2016-06-28 at 09:35 -0700, Joe Perches wrote:
> (adding Mathias Krause who did something similar via macros in 2014)
>
> https://lkml.org/lkml/2014/6/22/149
>
> On Tue, 2016-06-28 at 13:34 +0200, Emese Revfy wrote:
> >
> > I would like to introduce the initify gcc plugin. The kernel already
> > has
> > a mechanism to free up code and data memory that is only used during
> > kernel
> > or module initialization.
> > This plugin will teach the compiler to find more such code and data
> > that
> > can be freed after initialization. It reduces memory usage.
> > The initify gcc plugin can be useful for embedded systems.
> What happens to string deduplication when one string
> is in an init function and the same string is also used
> in a non-init function in the same compilation unit?
>
> foo.c
>
> __init void initfunc(void)
> {
> pr_info("%s: I'm here\n", __func__);
> }
>
> void runtimefunc(void)
> {
> pr_info("I'm here: %s\n", __func__);
> }
>
> In what section does the string "I'm here: %s\n" get placed
> or does it get placed into multiple sections?
Sorry, Joe can't type.
That was meant to be the identical string in both functions.
next prev parent reply other threads:[~2016-06-28 18:49 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-28 11:34 [PATCH v1 0/2] Introduce the initify gcc plugin Emese Revfy
2016-06-28 11:35 ` [PATCH v1 1/2] Add " Emese Revfy
2016-06-28 21:05 ` Rasmus Villemoes
2016-06-29 14:50 ` Kees Cook
2016-06-29 19:03 ` Emese Revfy
2016-06-28 11:36 ` [PATCH v1 2/2] Mark functions with the __nocapture attribute Emese Revfy
2016-06-28 16:43 ` Joe Perches
2016-06-28 20:40 ` Emese Revfy
2016-06-28 21:00 ` Joe Perches
2016-06-29 18:42 ` Emese Revfy
2016-06-30 0:12 ` Joe Perches
2016-07-01 14:03 ` Emese Revfy
2016-06-28 20:50 ` Rasmus Villemoes
2016-06-28 21:38 ` PaX Team
2016-06-28 22:41 ` Rasmus Villemoes
2016-06-29 18:39 ` Emese Revfy
2016-06-28 11:42 ` [PATCH v1 0/2] Introduce the initify gcc plugin Emese Revfy
2016-06-28 12:57 ` [kernel-hardening] " Mark Rutland
2016-06-28 16:14 ` Emese Revfy
2016-06-28 20:46 ` Kees Cook
2016-06-29 8:21 ` Mark Rutland
2016-06-29 17:52 ` Mark Rutland
2016-06-29 18:28 ` Emese Revfy
2016-06-28 16:35 ` Joe Perches
2016-06-28 18:48 ` Joe Perches [this message]
2016-06-28 19:02 ` Rasmus Villemoes
2016-06-28 20:29 ` Emese Revfy
2016-06-28 17:00 ` Mathias Krause
2016-06-28 20:29 ` Emese Revfy
2016-06-28 21:49 ` Joe Perches
2016-06-28 22:07 ` [kernel-hardening] " Valdis.Kletnieks
2016-06-28 23:54 ` Joe Perches
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=1467139734.24287.45.camel@perches.com \
--to=joe@perches.com \
--cc=akpm@linux-foundation.org \
--cc=arnd@arndb.de \
--cc=benh@kernel.crashing.org \
--cc=catalin.marinas@arm.com \
--cc=david.brown@linaro.org \
--cc=jlayton@poochiereds.net \
--cc=keescook@chromium.org \
--cc=kernel-hardening@lists.openwall.com \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=linux@rasmusvillemoes.dk \
--cc=minipli@googlemail.com \
--cc=minipli@ld-linux.so \
--cc=mmarek@suse.com \
--cc=pageexec@freemail.hu \
--cc=re.emese@gmail.com \
--cc=spender@grsecurity.net \
--cc=tglx@linutronix.de \
--cc=yamada.masahiro@socionext.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox