[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20160628222956.8142716b310953fa6b1af1c4@gmail.com>
Date: Tue, 28 Jun 2016 22:29:56 +0200
From: Emese Revfy <re.emese@...il.com>
To: Rasmus Villemoes <linux@...musvillemoes.dk>
Cc: Joe Perches <joe@...ches.com>, kernel-hardening@...ts.openwall.com,
Mathias Krause <minipli@...glemail.com>, pageexec@...email.hu,
spender@...ecurity.net, mmarek@...e.com, keescook@...omium.org,
linux-kernel@...r.kernel.org, yamada.masahiro@...ionext.com,
linux-kbuild@...r.kernel.org, minipli@...linux.so,
linux@...linux.org.uk, catalin.marinas@....com,
david.brown@...aro.org, benh@...nel.crashing.org,
tglx@...utronix.de, akpm@...ux-foundation.org,
jlayton@...chiereds.net, arnd@...db.de
Subject: Re: [PATCH v1 0/2] Introduce the initify gcc plugin
On Tue, 28 Jun 2016 21:02:54 +0200
Rasmus Villemoes <linux@...musvillemoes.dk> wrote:
> It'll get placed in multiple sections by the compiler, and nothing bad
> happens. String deduplication is something the linker does to sections
> equipped with appropriate flags. So in this case that of course means
Note that I didn't add such flags to my sections yet, but I have it on my todo list.
> that the kernel image itself would be slightly bigger, while the used
> data after init would be the same. But I don't think there's a lot of
> these cases. (Also, "initfunc" would at least vanish).
--
Emese
Powered by blists - more mailing lists