Received: by 2002:a25:86ce:0:0:0:0:0 with SMTP id y14csp392746ybm; Mon, 20 May 2019 18:45:47 -0700 (PDT) X-Google-Smtp-Source: APXvYqwxxbCL/EjV8ElsLaNr+y4dU8AVdEYA5dMUBolJienC33Buo72IETcmB9+p7GVINXQiiSX4 X-Received: by 2002:a63:c64c:: with SMTP id x12mr78268432pgg.379.1558403147365; Mon, 20 May 2019 18:45:47 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1558403147; cv=none; d=google.com; s=arc-20160816; b=hIbwv83FxCUVucJFihAGEX3EVC27P2KRuH9NeDB3w2a1laTKbQwZ8dK810YJDBNqXh /x/8dQixKAwdnkCKrB5i77unQ4vub9MCP2wB+D65tvHRmRk0sk1HAAOeK9Z4hfyyyQB9 etvHCd8POju8jutilYH/WasYLCjPYBzou2L6ChVwTZfC0+6jJ9ks8GnXC7HWnAQpUqha sqrM+nPBPVCcx9/P5wmnPAV0xro7CZnFfo2EPevI19pArw+6Tz/8OS6pK5w5uUm/Hldc CzUKki944gJ+TJk8Bm8+i/24b5Tzl3G+CoIbqwwp0W00TFkV0RcDlsR+6EaMXlLGITnq XqpQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding:mime-version :references:in-reply-to:from:subject:cc:to:message-id:date; bh=DddwT0x8zMq9ZypXaz8ht9er9UPkaa5SLfsnPfZzPmE=; b=EkMcow2oH88Ydl8K1WS0jHk0mI/v+6c8qXAeIyGcoywDtzBrIBoZmpeBQ/YS3PowZg +nHCfUQbz+VgYfviYTlrDMYdrAh6LZIwDD5t8CRoBgs/pNAYeVvn62lWv4wvD+XFtADk vo3qdf1cjr1p+/NEdHLNccE/MMQhpIwMwUPrgLLbe4ELeUdvoEbuQRGleVCsMPlRcQlH ebbAlEreVFfhNLWpjFEOWE/f0tNS7KG4WlSkjuhZgOKwlIgTKo2Qvz3pHKC8dAHfFq7l 86fBDXBaIk4ietOmvj955WBAJWKnWyxo/SpPX3854Jpgz91WMWfbqx812qLC1Fl+Zzdf y6Bw== 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 a5si73454pff.97.2019.05.20.18.45.20; Mon, 20 May 2019 18:45:47 -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 S1727538AbfEUBnk (ORCPT + 99 others); Mon, 20 May 2019 21:43:40 -0400 Received: from shards.monkeyblade.net ([23.128.96.9]:60738 "EHLO shards.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727108AbfEUBnj (ORCPT ); Mon, 20 May 2019 21:43:39 -0400 Received: from localhost (unknown [IPv6:2601:601:9f80:35cd::3d8]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (Client did not present a certificate) (Authenticated sender: davem-davemloft) by shards.monkeyblade.net (Postfix) with ESMTPSA id AC23214249739; Mon, 20 May 2019 18:43:38 -0700 (PDT) Date: Mon, 20 May 2019 18:43:36 -0700 (PDT) Message-Id: <20190520.184336.743103388474716249.davem@davemloft.net> To: rick.p.edgecombe@intel.com Cc: linux-kernel@vger.kernel.org, peterz@infradead.org, linux-mm@kvack.org, mroos@linux.ee, mingo@redhat.com, namit@vmware.com, luto@kernel.org, bp@alien8.de, netdev@vger.kernel.org, dave.hansen@intel.com, sparclinux@vger.kernel.org Subject: Re: [PATCH v2] vmalloc: Fix issues with flush flag From: David Miller In-Reply-To: References: <3e7e674c1fe094cd8dbe0c8933db18be1a37d76d.camel@intel.com> <20190520.203320.621504228022195532.davem@davemloft.net> X-Mailer: Mew version 6.8 on Emacs 26.1 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.5.12 (shards.monkeyblade.net [149.20.54.216]); Mon, 20 May 2019 18:43:39 -0700 (PDT) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org From: "Edgecombe, Rick P" Date: Tue, 21 May 2019 01:20:33 +0000 > Should it handle executing an unmapped page gracefully? Because this > change is causing that to happen much earlier. If something was relying > on a cached translation to execute something it could find the mapping > disappear. Does this work by not mapping any kernel mappings at the beginning, and then filling in the BPF mappings in response to faults?