From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-2.6 required=3.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_PASS, USER_AGENT_MUTT autolearn=unavailable autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id CE7A3C169C4 for ; Mon, 11 Feb 2019 19:01:39 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 972BE20863 for ; Mon, 11 Feb 2019 19:01:39 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (1024-bit key) header.d=alien8.de header.i=@alien8.de header.b="AF/C1MIM" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1733300AbfBKTBR (ORCPT ); Mon, 11 Feb 2019 14:01:17 -0500 Received: from mail.skyhub.de ([5.9.137.197]:48862 "EHLO mail.skyhub.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1733277AbfBKTBQ (ORCPT ); Mon, 11 Feb 2019 14:01:16 -0500 Received: from zn.tnic (p200300EC2BC7A10074DEFDFE3AD6CF32.dip0.t-ipconnect.de [IPv6:2003:ec:2bc7:a100:74de:fdfe:3ad6:cf32]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.skyhub.de (SuperMail on ZX Spectrum 128k) with ESMTPSA id 99AB21EC01AF; Mon, 11 Feb 2019 20:01:14 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=alien8.de; s=dkim; t=1549911674; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:in-reply-to:in-reply-to: references:references; bh=qWpDfY9hdZigS4Dtjg1dc7Cbm4tCe4w1qekSQJB7WTQ=; b=AF/C1MIM5X+09YOUt8D3qKn3HVAOfhn+qR7SVoJP7VlW/9RiKKb8XDrl7Zd3X4x34F3OWA itb3pR9IU1oePmeRJRAkXZ9WkBzL2B8pr0SohcMKAN8/JjHenMUuFOgfVr3peRm/Rlddxu SFxivBRbCkhNC48c5HPHOLAKykBGhLw= Date: Mon, 11 Feb 2019 20:01:08 +0100 From: Borislav Petkov To: Nadav Amit Cc: Rick Edgecombe , Andy Lutomirski , Ingo Molnar , LKML , X86 ML , "H. Peter Anvin" , Thomas Gleixner , Dave Hansen , Peter Zijlstra , Damian Tometzki , linux-integrity , LSM List , Andrew Morton , Kernel Hardening , Linux-MM , Will Deacon , Ard Biesheuvel , Kristen Carlson Accardi , "Dock, Deneen T" , Kees Cook , Dave Hansen , Masami Hiramatsu Subject: Re: [PATCH v2 10/20] x86: avoid W^X being broken during modules loading Message-ID: <20190211190108.GP19618@zn.tnic> References: <20190129003422.9328-1-rick.p.edgecombe@intel.com> <20190129003422.9328-11-rick.p.edgecombe@intel.com> <20190211182956.GN19618@zn.tnic> <1533F2BB-2284-499B-9912-6D74D0B87BC1@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <1533F2BB-2284-499B-9912-6D74D0B87BC1@gmail.com> User-Agent: Mutt/1.10.1 (2018-07-13) Sender: owner-linux-security-module@vger.kernel.org Precedence: bulk List-ID: On Mon, Feb 11, 2019 at 10:45:26AM -0800, Nadav Amit wrote: > Are you sure about that? This path is still used when modules are loaded. Yes, I'm sure. Loading a module does a gazillion things so saving a couple of insns - yes, boot_cpu_has() is usually a RIP-relative MOV and a TEST - doesn't show even as a blip on any radar. -- Regards/Gruss, Boris. Good mailing practices for 400: avoid top-posting and trim the reply.