Received: by 2002:ac0:a582:0:0:0:0:0 with SMTP id m2-v6csp832958imm; Thu, 4 Oct 2018 04:13:41 -0700 (PDT) X-Google-Smtp-Source: ACcGV62XXjCuhMolVWBKZEE7SX+jAk8Ef1FTLvbwaUyXrVpgcwl1mx2BHhxK/iqub6+D6kZ3eEty X-Received: by 2002:a65:5147:: with SMTP id g7-v6mr5408792pgq.252.1538651621037; Thu, 04 Oct 2018 04:13:41 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1538651621; cv=none; d=google.com; s=arc-20160816; b=bbWTxfHqTj6SKdO4y2D88Gz181kC3u2Kp2oj93eORN4/bcFZrFYyh3yPakPKG1RQCM +nI+z8Eahx/ToqX2gJ4CWfGe2HFt3qPgHIpS3oFFLEspB8hrcoziDfI1PYzj1sqXrvo7 vJd97akkvDetOOsxAmIKmZiYkoslIa06VkUQczcBAig2mqyune0bno1NK9UW/xb1oR6C R+o92wbj/qa4NPEyi6eMwRvoVER4c9YjRUg/laxukiLVF4tV/7hASENEwDeRTSHbDy3S yR6Ixw48tisNe5/z9bNQXntfkKuWttfIx/1/HnmeVFgkwTG5DSuEZA895oxH3cVsELTO WsWA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:message-id:subject:cc :to:from:date; bh=07XI+qy3Fk659CNu4Ipec/T7xdBJL1lDGiLRGfpsP9g=; b=bdtCCR6wTyAdwWISiu/mP+ele6qzHGPePbCq8cuRQ0RABI1sslDIUxR+xQFNQ9Ovzp zN3PLZjVYhFC17Hgr8YbXDdTdpWp53yRqr7DJYY7lLNMY2brawAjOkDa0MCzbDL18Wgs +TThuJKrACMaYFZHNEz+K/0YMkGyCSG23VFP+NowpkKrm2Dq/a9Rdq6QQ8yeYKiLSONX jmQVu/z/tKqe7D7utfxEnTRJuAQVhfqGZCNrp8ZA2p03JnjqZz76hM3bsiMJVr9UwJmx U2lx5+RlJBceQwY3hcGruoQRX/JJy7dXlLiwHepxnjWEIs//LqbZsIaolQaFVhZUuajJ +eRQ== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id z20-v6si1037519pfe.245.2018.10.04.04.13.25; Thu, 04 Oct 2018 04:13:41 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727674AbeJDSFx (ORCPT + 99 others); Thu, 4 Oct 2018 14:05:53 -0400 Received: from mail.skyhub.de ([5.9.137.197]:37910 "EHLO mail.skyhub.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727245AbeJDSFw (ORCPT ); Thu, 4 Oct 2018 14:05:52 -0400 X-Virus-Scanned: Nedap ESD1 at mail.skyhub.de Received: from mail.skyhub.de ([127.0.0.1]) by localhost (blast.alien8.de [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id EHGZR2f9PUKl; Thu, 4 Oct 2018 13:13:04 +0200 (CEST) Received: from zn.tnic (p200300EC2BCA7500329C23FFFEA6A903.dip0.t-ipconnect.de [IPv6:2003:ec:2bca:7500:329c:23ff:fea6:a903]) (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 3A7EB1EC02D1; Thu, 4 Oct 2018 13:13:04 +0200 (CEST) Date: Thu, 4 Oct 2018 13:12:58 +0200 From: Borislav Petkov To: Paul Menzel Cc: =?utf-8?B?SsO2cmcgUsO2ZGVs?= , Thomas Gleixner , linux-mm@kvack.org, x86@kernel.org, LKML Subject: Re: x86/mm: Found insecure W+X mapping at address (ptrval)/0xc00a0000 Message-ID: <20181004111258.GJ1864@zn.tnic> References: <20181003212255.GB28361@zn.tnic> <20181004080321.GA3630@8bytes.org> <20181004081429.GB1864@zn.tnic> <6cbb9135-7e89-748f-1d55-ac105a9f8091@molgen.mpg.de> <20181004084946.GD1864@zn.tnic> <20181004105443.GH1864@zn.tnic> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.10.1 (2018-07-13) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, Oct 04, 2018 at 01:00:42PM +0200, Paul Menzel wrote: > While here you write, it did not. Read again what I said: > and I did try marking the ISA range RO in mark_rodata_ro() but the > machine wouldn't boot after. and the code I pasted has this: // init_memory_mapping(0, ISA_END_ADDRESS); which is disabling the direct mapping of the ISA range. Two very different things. And you don't absolutely need to try it because it would simply move the warning to another address, just like it happened on my system. Because looking at your dmesg, that E350M1 machine is very similar to the laptop I have. But feel free if you have time on your hands... :) > Sorry I do not understand the question. I carry the SSD drive with > me, and connect it to the ASRock E350M1 (64-bit) or to the Lenovo > X60 laptop and boot from it from both systems. So it is an OS installation which you swap between two machines. I admit, it is the first time I hear of such a use case. In that case, yes, bitness does matter. -- Regards/Gruss, Boris. Good mailing practices for 400: avoid top-posting and trim the reply.