Date: Thu, 11 Apr 2019 10:29:43 -0700 From: Kees Cook <keescook@...omium.org> To: Alexander Potapenko <glider@...gle.com> Cc: Masahiro Yamada <yamada.masahiro@...ionext.com>, James Morris <jmorris@...ei.org>, "Serge E. Hallyn" <serge@...lyn.com>, linux-security-module <linux-security-module@...r.kernel.org>, linux-kbuild <linux-kbuild@...r.kernel.org>, Nick Desaulniers <ndesaulniers@...gle.com>, Kostya Serebryany <kcc@...gle.com>, Dmitry Vyukov <dvyukov@...gle.com>, Sandeep Patil <sspatil@...roid.com>, Laura Abbott <labbott@...hat.com>, Kernel Hardening <kernel-hardening@...ts.openwall.com> Subject: Re: [PATCH v4 2/3] initmem: introduce CONFIG_INIT_ALL_HEAP On Thu, Apr 11, 2019 at 1:39 AM Alexander Potapenko <glider@...gle.com> wrote: > > On Wed, Apr 10, 2019 at 6:09 PM Kees Cook <keescook@...omium.org> wrote: > > > > On Wed, Apr 10, 2019 at 6:18 AM Alexander Potapenko <glider@...gle.com> wrote: > > > > > > This config option adds the possibility to initialize newly allocated > > > pages and heap objects with a 0xAA pattern. > > > There's already a number of places where allocations are initialized > > > based on the presence of __GFP_ZERO flag. We just change this code so > > > that under CONFIG_INIT_ALL_HEAP these allocations are always initialized > > > with either 0x00 or 0xAA depending on the __GFP_ZERO. > > > > Why not just make __GFP_ZERO unconditional instead? This looks like > > it'd be simpler and not need arch-specific implementation? > > Right, but it would mean we can only initialize with 0x00 pattern. > I believe that for testing purposes a nonzero pattern is better, Can it be implemented in a way that isn't arch-specific? I'd really like to have a general solution that works immediately for all architectures. (Can't everything just use a memset?) > because it'll not only assure the execution is deterministic, but will > also uncover logic bugs earlier (see the discussion at > https://reviews.llvm.org/D54604?id=174471) > For hardening purposes the pattern shouldn't matter much. So, for hardening, it actually does matter but only in certain cases. On 64-bit, a 0xAA... pointer will have the high bit set, so it'll land in the non-canonical memory range, which is good. For 32-bit, 0xAA... will be in userspace (TASK_SIZE is 0xC0000000). In the above URL I see now that 32-bit pointer init gets 0x000000AA, which is good, but for heap init, types aren't known. So perhaps use 0x000000AA for 32-bit and 0xAA... for 64-bit heap init? (0xAA... has stronger properties since there have been NULL page mapping bypass flaws in the (recent!) past, so I could see keeping that for 64-bit instead of just using 0-init everywhere.) > If you think arch-specific code is too much of a trouble, we could > implement clear_page_pattern() using memset() on every architecture, > but allow the user to choose between slow (0xAA) and production (0x00) > modes. How about 32-bit use 0x00, 64-bit use 0xAA (and provide per-arch speed-ups with a generic "slow" version for all the other architectures?) -Kees -- Kees Cook
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.