[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20190731193509.GG4700@bombadil.infradead.org>
Date: Wed, 31 Jul 2019 12:35:09 -0700
From: Matthew Wilcox <willy@...radead.org>
To: Laura Abbott <labbott@...hat.com>
Cc: Alexander Potapenko <glider@...gle.com>,
kernel test robot <rong.a.chen@...el.com>,
Linus Torvalds <torvalds@...ux-foundation.org>,
Kees Cook <keescook@...omium.org>,
Christoph Lameter <cl@...ux.com>,
Masahiro Yamada <yamada.masahiro@...ionext.com>,
"Serge E. Hallyn" <serge@...lyn.com>,
Nick Desaulniers <ndesaulniers@...gle.com>,
Kostya Serebryany <kcc@...gle.com>,
Dmitry Vyukov <dvyukov@...gle.com>,
Sandeep Patil <sspatil@...roid.com>,
Randy Dunlap <rdunlap@...radead.org>,
Jann Horn <jannh@...gle.com>,
Mark Rutland <mark.rutland@....com>,
Marco Elver <elver@...gle.com>,
Andrew Morton <akpm@...ux-foundation.org>,
LKML <linux-kernel@...r.kernel.org>, LKP <lkp@...org>,
linux-mm@...ck.org
Subject: Re: [PATCH] mm: slub: Fix slab walking for init_on_free
On Wed, Jul 31, 2019 at 03:32:40PM -0400, Laura Abbott wrote:
> Fix this by ensuring the value we set with set_freepointer is either NULL
> or another value in the chain.
>
> Reported-by: kernel test robot <rong.a.chen@...el.com>
> Signed-off-by: Laura Abbott <labbott@...hat.com>
Fixes: 6471384af2a6 ("mm: security: introduce init_on_alloc=1 and init_on_free=1 boot options")
Powered by blists - more mailing lists