[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20200305080756.GB19839@kadam>
Date: Thu, 5 Mar 2020 11:07:56 +0300
From: Dan Carpenter <dan.carpenter@...cle.com>
To: Kees Cook <keescook@...omium.org>
Cc: "open list:ANDROID DRIVERS" <devel@...verdev.osuosl.org>,
Jann Horn <jannh@...gle.com>,
Peter Zijlstra <peterz@...radead.org>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
LKML <linux-kernel@...r.kernel.org>,
Arve Hjønnevåg <arve@...roid.com>,
Ingo Molnar <mingo@...hat.com>,
Alexander Potapenko <glider@...gle.com>,
Joe Perches <joe@...ches.com>,
Dmitriy Vyukov <dvyukov@...gle.com>,
Todd Kjos <tkjos@...gle.com>
Subject: Re: [PATCH v2 2/3] binder: do not initialize locals passed to
copy_from_user()
On Wed, Mar 04, 2020 at 10:13:40AM -0800, Kees Cook wrote:
> On Tue, Mar 03, 2020 at 12:38:32PM +0300, Dan Carpenter wrote:
> > The real fix is to initialize everything manually, the automated
> > initialization is a hardenning feature which many people will disable.
>
> I cannot disagree more with this sentiment. Linus has specifically said he
> wants this initialization on by default[1],
Fine, but as long as it's a configurable thing then we need to manually
initialize as well or it's still a CVE etc. It will take a while before
we drop support for old versions of GCC as well.
regards,
dan carpenter
Powered by blists - more mailing lists