From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S934311AbcLTRaB (ORCPT ); Tue, 20 Dec 2016 12:30:01 -0500 Received: from smtprelay0130.hostedemail.com ([216.40.44.130]:37301 "EHLO smtprelay.hostedemail.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S933809AbcLTRaB (ORCPT ); Tue, 20 Dec 2016 12:30:01 -0500 X-Session-Marker: 6A6F6540706572636865732E636F6D X-Spam-Summary: 2,0,0,,d41d8cd98f00b204,joe@perches.com,:::::::::::::::::::::::::::::,RULES_HIT:41:355:379:541:988:989:1260:1277:1311:1313:1314:1345:1359:1373:1437:1515:1516:1518:1534:1538:1568:1593:1594:1711:1714:1730:1747:1777:1792:2198:2199:2393:2559:2562:2828:3138:3139:3140:3141:3142:3622:3865:3866:3867:3868:3871:3874:4321:5007:6742:7903:10004:10400:10848:11232:11658:11914:12048:12740:12760:12895:13069:13311:13357:13439:14659:21080:30003:30012:30054:30091,0,RBL:none,CacheIP:none,Bayesian:0.5,0.5,0.5,Netcheck:none,DomainCache:0,MSF:not bulk,SPF:fn,MSBL:0,DNSBL:none,Custom_rules:0:0:0,LFtime:1,LUA_SUMMARY:none X-HE-Tag: grape32_91261512c6957 X-Filterd-Recvd-Size: 1682 Message-ID: <1482254995.1984.20.camel@perches.com> Subject: Designated initializers, struct randomization and addressing? From: Joe Perches To: Kees Cook , linux-kernel@vger.kernel.org, Julia Lawall , Dan Carpenter Cc: Oleg Drokin , Andreas Dilger , James Simmons , Greg Kroah-Hartman , "John L. Hammond" , Emoly Liu , Vitaly Fertman , Bruno Faccini , Bruce Korb , lustre-devel@lists.lustre.org, devel@driverdev.osuosl.org Date: Tue, 20 Dec 2016 09:29:55 -0800 In-Reply-To: <20161217010045.GA140343@beast> References: <20161217010045.GA140343@beast> Content-Type: text/plain; charset="ISO-8859-1" X-Mailer: Evolution 3.22.1-0ubuntu2 Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, 2016-12-16 at 17:00 -0800, Kees Cook wrote: > Prepare to mark sensitive kernel structures for randomization by making sure they're using designated initializers. About the designated initializer patches, which by themselves are fine of course, and the fundamental randomization plugin, c guarantees that struct member ordering is as specified. how is the code to be verified so that any use of things like offsetof and any address/indexing is not impacted?