From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org [172.17.192.35]) by mail.linuxfoundation.org (Postfix) with ESMTPS id 7986D98D for ; Mon, 24 Aug 2015 17:39:54 +0000 (UTC) Received: from mail3-relais-sop.national.inria.fr (mail3-relais-sop.national.inria.fr [192.134.164.104]) by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 8F0FA12E for ; Mon, 24 Aug 2015 17:39:53 +0000 (UTC) Date: Mon, 24 Aug 2015 19:39:49 +0200 (CEST) From: Julia Lawall To: Andy Lutomirski In-Reply-To: Message-ID: References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Cc: Jiri Kosina , "ksummit-discuss@lists.linuxfoundation.org" , Emily Ratliff Subject: Re: [Ksummit-discuss] [TECH TOPIC] Kernel Hardening List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , > One thing that grsecurity addresses (partially or fully? I haven't > looked that closely): we have tons of static, non-const data structure > that contain function pointers, and we can't make them const because > they get filled in when things are initialized. Grsecurity mitigates > this with some combination of compiler plugins and pax_open_kernel, > but we could probably come up with a more straightforward solution. > We could add an ro_after_init section, or we could even have a section > for things that are const but are writable through a special function. Would it be helpful/possible to make a substructure for the constant parts? julia