Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756047Ab0BHB6X (ORCPT ); Sun, 7 Feb 2010 20:58:23 -0500 Received: from terminus.zytor.com ([198.137.202.10]:49237 "EHLO mail.zytor.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753211Ab0BHB6V (ORCPT ); Sun, 7 Feb 2010 20:58:21 -0500 Message-ID: <4B6F6EBB.5070106@zytor.com> Date: Sun, 07 Feb 2010 17:54:03 -0800 From: "H. Peter Anvin" User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.7) Gecko/20100120 Fedora/3.0.1-1.fc11 Thunderbird/3.0.1 MIME-Version: 1.0 To: Rusty Russell CC: Andi Kleen , Siarhei Liakh , linux-kernel@vger.kernel.org, linux-security-module@vger.kernel.org, linux-next@vger.kernel.org, Arjan van de Ven , James Morris , Andrew Morton , Andi Kleen , Thomas Gleixner , Ingo Molnar , Stephen Rothwell , Dave Jones Subject: Re: [PATCH v8] RO/NX protection for loadable kernel modules References: <817ecb6f1001311522q52bf4eebmb748c486dcd5ad35@mail.gmail.com> <873a1jdyrg.fsf@basil.nowhere.org> <201002081215.31527.rusty@rustcorp.com.au> In-Reply-To: <201002081215.31527.rusty@rustcorp.com.au> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 780 Lines: 22 On 02/07/2010 05:45 PM, Rusty Russell wrote: > > Strict RO/NX protection. But without the option enabled, the patch gives > best-effort protection, which is nice (for no additional space). > Since Linux kernel modules are actually .o's, not .so's, in theory we could bundle the sections together by type. There could still be external fragmentation, of course, but on most systems module unload is relatively rare. -hpa -- H. Peter Anvin, Intel Open Source Technology Center I work for Intel. I don't speak on their behalf. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/