Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754135AbdDDOHp (ORCPT ); Tue, 4 Apr 2017 10:07:45 -0400 Received: from mail-oi0-f53.google.com ([209.85.218.53]:36755 "EHLO mail-oi0-f53.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752432AbdDDOHo (ORCPT ); Tue, 4 Apr 2017 10:07:44 -0400 MIME-Version: 1.0 X-Originating-IP: [176.63.54.97] In-Reply-To: <20170329210219.GA39900@beast> References: <20170329210219.GA39900@beast> From: Miklos Szeredi Date: Tue, 4 Apr 2017 16:07:42 +0200 Message-ID: Subject: Re: [PATCH] ovl: Use designated initializers To: Kees Cook Cc: linux-kernel@vger.kernel.org, "linux-unionfs@vger.kernel.org" Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 454 Lines: 13 On Wed, Mar 29, 2017 at 11:02 PM, Kees Cook wrote: > Prepare to mark sensitive kernel structures for randomization by making > sure they're using designated initializers. These were identified during > allyesconfig builds of x86, arm, and arm64, with most initializer fixes > extracted from grsecurity. > > For these cases, use { }, which will be zero-filled, instead of > undesignated NULLs. Queued up for 4.12. Thanks, Miklos