[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Tue, 12 Mar 2019 02:05:27 +0300
From: Alexander Popov <alex.popov@...ux.com>
To: Kees Cook <keescook@...omium.org>, linux-kernel@...r.kernel.org
Cc: Emese Revfy <re.emese@...il.com>,
Ard Biesheuvel <ard.biesheuvel@...aro.org>, Laura Abbott
<labbott@...hat.com>, Jann Horn <jannh@...gle.com>,
Alexander Potapenko <glider@...gle.com>,
kernel-hardening@...ts.openwall.com,
Ard Biesheuvel <ard.biesheuvel@...aro.org>, Arnd Bergmann <arnd@...db.de>,
Geert Uytterhoeven <geert@...ux-m68k.org>
Subject: Re: [PATCH 1/2] gcc-plugins: structleak: Generalize to all variable
types
Hello Kees, hello everyone,
On 12.02.2019 21:04, Kees Cook wrote:
> Building with CONFIG_GCC_PLUGIN_STRUCTLEAK_BYREF_ALL should give the
> kernel complete initialization coverage of all stack variables passed
> by reference, including padding (see lib/test_stackinit.c).
I would like to note that new STRUCTLEAK_BYREF_ALL initializes *less* stack
variables than STACKINIT, that was introduced earlier:
https://www.openwall.com/lists/kernel-hardening/2019/01/23/3
Citing the patches:
- the STACKINIT plugin "attempts to perform unconditional initialization of all
stack variables";
- the STRUCTLEAK_BYREF_ALL feature "gives the kernel complete initialization
coverage of all stack variables passed by reference".
I.e. stack variables not passed by reference are not initialized by
STRUCTLEAK_BYREF_ALL.
Kees, what do you think about adding such cases to your lib/test_stackinit.c?
This simple example demonstrates the idea:
diff --git a/lib/test_stackinit.c b/lib/test_stackinit.c
index 13115b6..f9ef313 100644
--- a/lib/test_stackinit.c
+++ b/lib/test_stackinit.c
@@ -320,9 +320,18 @@ static noinline __init int leaf_switch_2_none(unsigned long sp, bool fill,
DEFINE_TEST_DRIVER(switch_1_none, uint64_t, SCALAR);
DEFINE_TEST_DRIVER(switch_2_none, uint64_t, SCALAR);
+struct x {
+ int x1;
+ int x2;
+ int x3;
+};
+
static int __init test_stackinit_init(void)
{
unsigned int failures = 0;
+ struct x _x;
+
+ printk("uninitialized struct fields sum: %d\n", _x.x1 + _x.x2 + _x.x3);
#define test_scalars(init) do { \
failures += test_u8_ ## init (); \
Kernel output:
root@vm:~# insmod /lib/modules/5.0.0+/kernel/lib/test_stackinit.ko
[ 40.534622] uninitialized struct fields sum: -727800841
Best regards,
Alexander
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.
