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=-10.3 required=3.0 tests=BAYES_00, HEADER_FROM_DIFFERENT_DOMAINS,INCLUDES_PATCH,MAILING_LIST_MULTI,NICE_REPLY_A, SPF_HELO_NONE,SPF_PASS,USER_AGENT_SANE_1 autolearn=ham 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 B11FEC433ED for ; Tue, 18 May 2021 10:45:27 +0000 (UTC) Received: from kanga.kvack.org (kanga.kvack.org [205.233.56.17]) by mail.kernel.org (Postfix) with ESMTP id 60C0B611BF for ; Tue, 18 May 2021 10:45:27 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 60C0B611BF Authentication-Results: mail.kernel.org; dmarc=none (p=none dis=none) header.from=suse.cz Authentication-Results: mail.kernel.org; spf=pass smtp.mailfrom=owner-linux-mm@kvack.org Received: by kanga.kvack.org (Postfix) id D84F18D0017; Tue, 18 May 2021 06:45:26 -0400 (EDT) Received: by kanga.kvack.org (Postfix, from userid 40) id D5BF98D0001; Tue, 18 May 2021 06:45:26 -0400 (EDT) X-Delivered-To: int-list-linux-mm@kvack.org Received: by kanga.kvack.org (Postfix, from userid 63042) id C0F848D0017; Tue, 18 May 2021 06:45:26 -0400 (EDT) X-Delivered-To: linux-mm@kvack.org Received: from forelay.hostedemail.com (smtprelay0217.hostedemail.com [216.40.44.217]) by kanga.kvack.org (Postfix) with ESMTP id 8E8BC8D0001 for ; Tue, 18 May 2021 06:45:26 -0400 (EDT) Received: from smtpin15.hostedemail.com (10.5.19.251.rfc1918.com [10.5.19.251]) by forelay01.hostedemail.com (Postfix) with ESMTP id 22ED7180AD830 for ; Tue, 18 May 2021 10:45:26 +0000 (UTC) X-FDA: 78154020252.15.414F3CF Received: from mx2.suse.de (mx2.suse.de [195.135.220.15]) by imf09.hostedemail.com (Postfix) with ESMTP id 49DCE6000115 for ; Tue, 18 May 2021 10:45:23 +0000 (UTC) X-Virus-Scanned: by amavisd-new at test-mx.suse.de Received: from relay2.suse.de (unknown [195.135.221.27]) by mx2.suse.de (Postfix) with ESMTP id 6F7C6AFBD; Tue, 18 May 2021 10:45:24 +0000 (UTC) Subject: Re: [PATCH v10 22/33] mm/filemap: Add __folio_lock_or_retry From: Vlastimil Babka To: "Matthew Wilcox (Oracle)" , akpm@linux-foundation.org Cc: linux-fsdevel@vger.kernel.org, linux-mm@kvack.org, linux-kernel@vger.kernel.org, Christoph Hellwig , Jeff Layton References: <20210511214735.1836149-1-willy@infradead.org> <20210511214735.1836149-23-willy@infradead.org> <76184de4-4ab9-0f04-ab37-8637f4b22566@suse.cz> Message-ID: Date: Tue, 18 May 2021 12:45:24 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.10.1 MIME-Version: 1.0 In-Reply-To: <76184de4-4ab9-0f04-ab37-8637f4b22566@suse.cz> Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit Authentication-Results: imf09.hostedemail.com; dkim=none; dmarc=none; spf=pass (imf09.hostedemail.com: domain of vbabka@suse.cz designates 195.135.220.15 as permitted sender) smtp.mailfrom=vbabka@suse.cz X-Rspamd-Server: rspam05 X-Rspamd-Queue-Id: 49DCE6000115 X-Stat-Signature: 4zbb4fchutnr6ga5br74nxg1rrsrxc5d X-HE-Tag: 1621334723-36535 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 5/18/21 12:38 PM, Vlastimil Babka wrote: >> --- a/mm/filemap.c >> +++ b/mm/filemap.c >> @@ -1623,20 +1623,18 @@ static int __folio_lock_async(struct folio *folio, struct wait_page_queue *wait) >> >> /* >> * Return values: >> - * 1 - page is locked; mmap_lock is still held. >> - * 0 - page is not locked. >> + * 1 - folio is locked; mmap_lock is still held. >> + * 0 - folio is not locked. >> * mmap_lock has been released (mmap_read_unlock(), unless flags had both >> * FAULT_FLAG_ALLOW_RETRY and FAULT_FLAG_RETRY_NOWAIT set, in >> * which case mmap_lock is still held. >> * >> * If neither ALLOW_RETRY nor KILLABLE are set, will always return 1 >> - * with the page locked and the mmap_lock unperturbed. >> + * with the folio locked and the mmap_lock unperturbed. >> */ >> -int __lock_page_or_retry(struct page *page, struct mm_struct *mm, >> +int __folio_lock_or_retry(struct folio *folio, struct mm_struct *mm, >> unsigned int flags) >> { >> - struct folio *folio = page_folio(page); >> - >> if (fault_flag_allow_retry_first(flags)) { >> /* >> * CAUTION! In this case, mmap_lock is not released > > A bit later in this branch, 'page' is accessed, but it no longer exists. And > thus as expected, it doesn't compile. Assuming it's fixed later, but > bisectability etc... Also, the switch from 'page' to &folio->page in there should probably have been done already in "[PATCH v10 20/33] mm/filemap: Add folio_lock_killable", not in this patch?