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=-3.6 required=3.0 tests=BAYES_00,DKIM_INVALID, DKIM_SIGNED,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE, SPF_PASS autolearn=no 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 16341C433B4 for ; Wed, 7 Apr 2021 02:40:13 +0000 (UTC) Received: from kanga.kvack.org (kanga.kvack.org [205.233.56.17]) by mail.kernel.org (Postfix) with ESMTP id 9223B61245 for ; Wed, 7 Apr 2021 02:40:12 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 9223B61245 Authentication-Results: mail.kernel.org; dmarc=none (p=none dis=none) header.from=infradead.org Authentication-Results: mail.kernel.org; spf=pass smtp.mailfrom=owner-linux-mm@kvack.org Received: by kanga.kvack.org (Postfix) id 1F10B6B0092; Tue, 6 Apr 2021 22:40:12 -0400 (EDT) Received: by kanga.kvack.org (Postfix, from userid 40) id 1A16E6B0093; Tue, 6 Apr 2021 22:40:12 -0400 (EDT) X-Delivered-To: int-list-linux-mm@kvack.org Received: by kanga.kvack.org (Postfix, from userid 63042) id 041386B0095; Tue, 6 Apr 2021 22:40:11 -0400 (EDT) X-Delivered-To: linux-mm@kvack.org Received: from forelay.hostedemail.com (smtprelay0094.hostedemail.com [216.40.44.94]) by kanga.kvack.org (Postfix) with ESMTP id D941C6B0092 for ; Tue, 6 Apr 2021 22:40:11 -0400 (EDT) Received: from smtpin35.hostedemail.com (10.5.19.251.rfc1918.com [10.5.19.251]) by forelay05.hostedemail.com (Postfix) with ESMTP id 8529B181AF5CC for ; Wed, 7 Apr 2021 02:40:11 +0000 (UTC) X-FDA: 78004016622.35.76033E3 Received: from casper.infradead.org (casper.infradead.org [90.155.50.34]) by imf12.hostedemail.com (Postfix) with ESMTP id 533EB130 for ; Wed, 7 Apr 2021 02:40:08 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=infradead.org; s=casper.20170209; h=In-Reply-To:Content-Type:MIME-Version: References:Message-ID:Subject:Cc:To:From:Date:Sender:Reply-To: Content-Transfer-Encoding:Content-ID:Content-Description; bh=uhOYkQO774jNDcmHPctjGjKcc0cOaB158ggEKqgnGnE=; b=TdNLBuS1SqLrQ7x+puvft7jQH1 obQFBOdNEkYnKl8JwCBFolMQ+7w1A6pcPaBT3PUdgAj1XG9sclZpJiRnCmP8vYYl87+pADZn7J60i 7RC2dmkaUaKw2PgQO4uVmpK4JrA683FC1xJDbW+mH6YBmz/pefufXu16U/oQDYCx775WT7mjZrvpV MFgS4dmDW3hgC3cwPLizUwZcA2t8nYdQTqPOESyCQQfBz7rDb/bkGtjk6AVD45A6u38sSMrkC2jJE te4KrLy8yMqJY0DOfl8QeJFBawMhYH0xnzAKEj2TzWt60OZsciXoQKg8B3i59OwkHl6V9w9HR2oDm ruIBRUEw==; Received: from willy by casper.infradead.org with local (Exim 4.94 #2 (Red Hat Linux)) id 1lTy6a-00Dm9H-Dr; Wed, 07 Apr 2021 02:39:47 +0000 Date: Wed, 7 Apr 2021 03:39:44 +0100 From: Matthew Wilcox To: Michel Lespinasse Cc: Linux-MM , Laurent Dufour , Peter Zijlstra , Michal Hocko , Rik van Riel , Paul McKenney , Andrew Morton , Suren Baghdasaryan , Joel Fernandes , Rom Lemarchand , Linux-Kernel Subject: Re: [RFC PATCH 29/37] fs: list file types that support speculative faults. Message-ID: <20210407023944.GZ2531743@casper.infradead.org> References: <20210407014502.24091-1-michel@lespinasse.org> <20210407014502.24091-30-michel@lespinasse.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20210407014502.24091-30-michel@lespinasse.org> X-Rspamd-Queue-Id: 533EB130 X-Stat-Signature: js6os5hozz5ei8eorto5nqrgqk6xnfuq X-Rspamd-Server: rspam02 Received-SPF: none (infradead.org>: No applicable sender policy available) receiver=imf12; identity=mailfrom; envelope-from=""; helo=casper.infradead.org; client-ip=90.155.50.34 X-HE-DKIM-Result: pass/pass X-HE-Tag: 1617763208-671606 X-Bogosity: Ham, tests=bogofilter, spamicity=0.000000, version=1.2.4 Sender: owner-linux-mm@kvack.org Precedence: bulk X-Loop: owner-majordomo@kvack.org List-ID: On Tue, Apr 06, 2021 at 06:44:54PM -0700, Michel Lespinasse wrote: > Add a speculative field to the vm_operations_struct, which indicates if > the associated file type supports speculative faults. > > Initially this is set for files that implement fault() with filemap_fault(). Ugh, no. This goes away if you don't call ->fault speculatively.