From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <linux-kernel-owner@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
        id S1031538AbdADQ5C (ORCPT <rfc822;w@1wt.eu>);
        Wed, 4 Jan 2017 11:57:02 -0500
Received: from mail-pg0-f44.google.com ([74.125.83.44]:36418 "EHLO
        mail-pg0-f44.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
        with ESMTP id S1752284AbdADQzz (ORCPT
        <rfc822;linux-kernel@vger.kernel.org>);
        Wed, 4 Jan 2017 11:55:55 -0500
Date: Wed, 4 Jan 2017 08:55:34 -0800
From: Stephen Hemminger <stephen@networkplumber.org>
To: Kees Cook <keescook@chromium.org>
Cc: Julia Lawall <julia.lawall@lip6.fr>, devel@driverdev.osuosl.org,
        Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
        LKML <linux-kernel@vger.kernel.org>,
        Bruno Faccini <bruno.faccini@intel.com>,
        Oleg Drokin <oleg.drokin@intel.com>,
        Vitaly Fertman <vitaly_fertman@xyratex.com>,
        Joe Perches <joe@perches.com>,
        Andreas Dilger <andreas.dilger@intel.com>,
        "John L. Hammond" <john.hammond@intel.com>,
        Bruce Korb <bruce.korb@gmail.com>, Emoly Liu <emoly.liu@intel.com>
Subject: Re: Designated initializers, struct randomization and addressing?
Message-ID: <20170104085534.7c4d2b07@xeon-e3>
In-Reply-To: <CAGXu5jKH=DxP_SzJ3=dtW5FFFKJWT4ymh8fqCJecX6dreDo0Tw@mail.gmail.com>
References: <20161217010045.GA140343@beast>
        <1482254995.1984.20.camel@perches.com>
        <CAGXu5jJUHZi5LUxFjG9XfKgipBpGYfdfUXM8q_xEWqQrqtq1Tw@mail.gmail.com>
        <alpine.DEB.2.20.1701040726310.2004@hadrien>
        <CAGXu5jKH=DxP_SzJ3=dtW5FFFKJWT4ymh8fqCJecX6dreDo0Tw@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org

On Tue, 3 Jan 2017 22:35:26 -0800
Kees Cook <keescook@chromium.org> wrote:

> For randstruct and constify, the automatic selection is done on
> structures with only function pointers. (Additional structures can be
> added via a compiler attribute marking.)
> 
> See is_pure_ops_struct():

Is there anyway to use this plugin to identify pure_ops structures not already marked as const?