Received: by 2002:a6b:fb09:0:0:0:0:0 with SMTP id h9csp797457iog; Wed, 29 Jun 2022 10:21:09 -0700 (PDT) X-Google-Smtp-Source: AGRyM1v/5t+qb0ByRfG+meYMddqDtKVDCAZyYwuVE4HA8pIDPILWRjtfs2tn4HxN+pKYioShJ+b/ X-Received: by 2002:a17:906:8459:b0:72a:5159:f455 with SMTP id e25-20020a170906845900b0072a5159f455mr414993ejy.764.1656523269465; Wed, 29 Jun 2022 10:21:09 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1656523269; cv=none; d=google.com; s=arc-20160816; b=FAw9jKUH9IA+pCMg0vYPlO/SbYY0jBWLqLdtiDhDjzkbXz58YXeky5iYAIemUbOVPi 4NFhuJOwOZn0DcORYjsjCyGpBSirfYftd3bOhF/FDNX+qb7kU8+vdW4hsgb+kNqDGFZd lYT0O764wBr9MF6DxcLL1K2SP9b7m88eJBLZwUJJ+3CVz47nPfJ916z7UDXV9YK1By72 ++mGg68Sap/UsMWUBA9+XZkM+v47OEtP51gwQsoQnZclgIVr2Mfha4KeQaSnDi09NAXY lgkFQQCjCOusYg0qcfotVcmTDCr62OsomSAKd6cXgV3C5VMHfGH8atGoH3uUXFcQNfex vDpw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:in-reply-to:content-disposition:mime-version :references:message-id:subject:cc:to:from:date:dkim-signature; bh=FEPFOn0xcSEPQj7BISgvQqKIvzUO50xW3yQt0RenuEs=; b=HJRNa70qBBQFcFP+VY9nvk5jCWCT0QkKEWUkdAkzWqMVahXuhgbJJAk4Jrys8nO7pb V+9e2yzeQDrpNpBjn7PpoxIHx7KxHWc1EWeUdWe9ku7zb95rI6WrouH1AQFO/8/sztSn 9MKQ7/b6b5n5dxaJp6+68Q5JjAVMOhpEhRrYg3IqgmhWrShX3HdXh3XKovZq14x1lNlI dWyUIybYierAOKrtoIjimMgVDUHjmYjzyqVZRdSwATgFyYBX0icW/BZzWqi60OcGrkcZ W0NfucqtR1KZnFrfIEYoOYv93Rilb+vF5w7gpCeckWGU7LqN1sv8dLprVEZP1e85VsgM IraQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@kernel.org header.s=k20201202 header.b=mmoROso5; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id m5-20020a509305000000b004356442b3a8si3683465eda.177.2022.06.29.10.20.43; Wed, 29 Jun 2022 10:21:09 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; dkim=pass header.i=@kernel.org header.s=k20201202 header.b=mmoROso5; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S231158AbiF2RPG (ORCPT + 99 others); Wed, 29 Jun 2022 13:15:06 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:58166 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S231676AbiF2RPD (ORCPT ); Wed, 29 Jun 2022 13:15:03 -0400 Received: from dfw.source.kernel.org (dfw.source.kernel.org [IPv6:2604:1380:4641:c500::1]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 5A9C83CA61 for ; Wed, 29 Jun 2022 10:15:00 -0700 (PDT) Received: from smtp.kernel.org (relay.kernel.org [52.25.139.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by dfw.source.kernel.org (Postfix) with ESMTPS id EAA2B61DE8 for ; Wed, 29 Jun 2022 17:14:59 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id 0932AC341CA; Wed, 29 Jun 2022 17:14:58 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1656522899; bh=nRYAO0YhqCfW4n6wXNQYaEZksNx77Z2cvSAAwv2BTXw=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=mmoROso54H2ZVFwQUwvRDiFyIa1hsR2lG/3lAZaePvTzKruFHeRsiGi4UC7PkEO8l qWc1TuTWvJNfGt8g2jUYIoiEpgw1IVFqpfuGxCEmq/KihSpGPzrNcam7ATayIKyxmW f84Z6R9fLtvGpaBEBiC5vfSbFRpz2dLWFplsUScFoVQLHclhAH0r2DGjW5wk0y5V0C 9aUICt/P0uNFQcTVjcc5lpqsp1Ao41rJTVA8vpojbxmL/unJ8H/UQaDityIYrRDKh7 LPIOQxETfTJbjRenZ5zm+rwcV+1EmrEfYCPDrqPdM/NXyS98sXiPnIlRoc+1bN6puO vZ9EP/kQpZRvQ== Date: Wed, 29 Jun 2022 10:14:57 -0700 From: Josh Poimboeuf To: Juergen Gross Cc: xen-devel@lists.xenproject.org, x86@kernel.org, linux-kernel@vger.kernel.org, Thomas Gleixner , Ingo Molnar , Borislav Petkov , Dave Hansen , "H. Peter Anvin" Subject: Re: [PATCH v2 2/3] x86: fix setup of brk area Message-ID: <20220629171457.amdsrgaxady55hds@treble> References: <20220623094608.7294-1-jgross@suse.com> <20220623094608.7294-3-jgross@suse.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <20220623094608.7294-3-jgross@suse.com> X-Spam-Status: No, score=-7.5 required=5.0 tests=BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,RCVD_IN_DNSWL_HI, SPF_HELO_NONE,SPF_PASS,T_SCC_BODY_TEXT_LINE autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi Juergen, It helps to actually Cc the person who broke it ;-) On Thu, Jun 23, 2022 at 11:46:07AM +0200, Juergen Gross wrote: > Commit e32683c6f7d2 ("x86/mm: Fix RESERVE_BRK() for older binutils") > put the brk area into the .bss..brk section (placed directly behind > .bss), Hm? It didn't actually do that. For individual translation units, it did rename the section from ".brk_reservation" to ".bss..brk". But then during linking it's still placed in .brk in vmlinux, just like before. > causing it not to be cleared initially. As the brk area is used > to allocate early page tables, these might contain garbage in not > explicitly written entries. > > This is especially a problem for Xen PV guests, as the hypervisor will > validate page tables (check for writable page tables and hypervisor > private bits) before accepting them to be used. There have been reports > of early crashes of PV guests due to illegal page table contents. > > Fix that by letting clear_bss() clear the brk area, too. While it does make sense to clear the brk area, I don't understand how my patch broke this. How was it getting cleared before? -- Josh