Received: by 2002:ac0:a5a6:0:0:0:0:0 with SMTP id m35-v6csp2725515imm; Mon, 10 Sep 2018 05:42:12 -0700 (PDT) X-Google-Smtp-Source: ANB0VdYBMn4Bb2Twybs3lp4DNElEiL/W0IXr35ruHirQnG2w1BN1d9mTRNsspX7eTmslCjz1gV4T X-Received: by 2002:a63:931b:: with SMTP id b27-v6mr11928861pge.143.1536583332606; Mon, 10 Sep 2018 05:42:12 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1536583332; cv=none; d=google.com; s=arc-20160816; b=ot6LOCLGjncZjoYlSsPF8FM+19DfCeFg6uzL4IN26I/DGrNe3X6EAIeFqYM0cnTWgU 3Fz+DY3eCIKp4zZbFRlvSvKZN8HIEwQGktMwalK3aZtMkYJryEYXdTiwfaNMLguEMlRb VR+qeMEcYmMyIKnSW8u78WdWOMMTvkns9Hu1KQKONpNFneMM+/XHFmLVEWUXsYpgPtqZ 6TX+803gzz+uXuri7MywoZH/SMsNYgP8+AOSGvPjfREB+VPkT1h99ctQ7WNdR0km+bbM iiXSS5g2oOor4u27Dsnent33a+G8V5RXfddx2s5BO4TSijt/YXYFNRlbTr6p4veDdeAb Ev2g== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:mime-version:message-id:date:subject:cc :to:from; bh=b6+ILveZU9pSJXgDvneLLKsUzfGHINnseKjUA0R4X2w=; b=aVo3by0eivGFKwCUOlTIk2Ci6j55s0l8SA3KV/yMHh3eenDlxoqbCchjYLXY4TfuEq m3C6vaTY+mSNp3OZLJ9xRQacuESPQVDqdtrq1lHu58VjFjyDK8lZvAwJj1+UBPzfDDKz DPc/4Nj4pZCK2LdP5K49jFYnzu3l+Nnn9+WTwMXKvWsZO2YR4yOkwSEzHAfXVzoSeTkM HZpepuUDYdcu1yH7UwFETUHHklCzUdXToegWmMvORbcdVa7aBikKdFnc4Q70RzKe5NOe 0igVaqv6gNfShDNH0kFURIUqgAbPrXSH979sis1G8qW1rxvHJHm69Eplwc9VukvQS4sP vy/w== 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 l5-v6si16597427pff.304.2018.09.10.05.41.57; Mon, 10 Sep 2018 05:42:12 -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 S1728611AbeIJRee (ORCPT + 99 others); Mon, 10 Sep 2018 13:34:34 -0400 Received: from mail.cn.fujitsu.com ([183.91.158.132]:52644 "EHLO heian.cn.fujitsu.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1727649AbeIJRee (ORCPT ); Mon, 10 Sep 2018 13:34:34 -0400 X-IronPort-AV: E=Sophos;i="5.43,368,1503331200"; d="scan'208";a="44733318" Received: from unknown (HELO cn.fujitsu.com) ([10.167.33.5]) by heian.cn.fujitsu.com with ESMTP; 10 Sep 2018 20:40:35 +0800 Received: from G08CNEXCHPEKD01.g08.fujitsu.local (unknown [10.167.33.80]) by cn.fujitsu.com (Postfix) with ESMTP id 5C4134B6ADFF; Mon, 10 Sep 2018 20:40:34 +0800 (CST) Received: from localhost (10.167.225.56) by G08CNEXCHPEKD01.g08.fujitsu.local (10.167.33.89) with Microsoft SMTP Server id 14.3.408.0; Mon, 10 Sep 2018 20:40:37 +0800 From: Chao Fan To: , , , , , , CC: , , , Chao Fan Subject: [PATCH v6 0/3] x86/boot/KASLR: Parse ACPI table and limit kaslr in immovable memory. Date: Mon, 10 Sep 2018 20:40:12 +0800 Message-ID: <20180910124015.18073-1-fanc.fnst@cn.fujitsu.com> X-Mailer: git-send-email 2.17.1 MIME-Version: 1.0 Content-Type: text/plain X-yoursite-MailScanner-ID: 5C4134B6ADFF.AC49D X-yoursite-MailScanner: Found to be clean X-yoursite-MailScanner-From: fanc.fnst@cn.fujitsu.com X-Spam-Status: No Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org ***Background: People reported that kaslr may randomly chooses some positions which are located in movable memory regions. This will break memory hotplug feature and make the movable memory chosen by KASLR can't be removed. ***Solutions: There should be a method to limit kaslr to choosing immovable memory regions, so there are 2 solutions: 1) Add a kernel parameter to specify the memory regions. 2) Get the information of memory hot-remove, then kaslr will know the right regions. In method 2, information about memory hot-remove is in ACPI tables, which will be parsed after start_kernel(), kaslr can't get the information. In method 1, users should know the regions address and specify in kernel parameter. In the earliest time, I tried to dig ACPI tabls to solve this problem. But I didn't splite the code in 'compressed/' and ACPI code, so the patch is hard to follow so refused by community. Somebody suggest to add a kernel parameter to specify the immovable memory so that limit kaslr in these regions. Then I make a new patchset. After several versions, Ingo gave a suggestion: https://www.mail-archive.com/linux-kernel@vger.kernel.org/msg1634024.html Follow Ingo's suggestion, imitate the ACPI code to parse the acpi tables, so that the kaslr can get necessary memory information in ACPI tables. I think ACPI code is an independent part, so copy the codes and functions to 'compressed/' directory, so that kaslr won't influence the initialization of ACPI. PATCH 1/3 Add acpitb.c to provide functions to parse ACPI code. PATCH 2/3 If CONFIG_MEMORY_HOTREMOVE enabled, walk all nodes and store the information of immovable memory regions. PATCH 3/3 According to the immovable memory regions, filter the immovable regions which KASLR can choose. ***Test results: - I did a very simple test, and it can get the memory information in bios and efi KVM guest machine, and put it by early printk. But no more tests, so it's with RFC tag. v1->v2: - Simplify some code. Follow Baoquan He's suggestion: - Reuse the head file of acpi code. v2->v3: - Test in more conditions, so remove the 'RFC' tag. - Change some comments. v3->v4: Follow Thomas Gleixner's suggetsion: - Put the whole efi related function into #define CONFIG_EFI and return false in the other stub. - Simplify two functions in head file. v4->v5: Follow Dou Liyang's suggestion: - Add more comments about some functions based on kernel code. - Change some typo in comments. - Clean useless variable. - Add check for the boundary of array. - Add check for 'movable_node' parameter v5->v6: Follow Baoquan He's suggestion: - Change some log. - Add the check for acpi_rsdp - Change some code logical to make code clear Any comments will be welcome. Chao Fan (3): x86/boot: Add acpitb.c to parse acpi tables x86/boot/KASLR: Walk srat tables to filter immovable memory x86/boot/KASLR: Limit kaslr to choosing the immovable memory arch/x86/boot/compressed/Makefile | 4 + arch/x86/boot/compressed/acpitb.c | 382 ++++++++++++++++++++++++++++++ arch/x86/boot/compressed/kaslr.c | 76 +++++- arch/x86/boot/compressed/misc.h | 8 + 4 files changed, 459 insertions(+), 11 deletions(-) create mode 100644 arch/x86/boot/compressed/acpitb.c -- 2.17.1