Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 5E44DC64ED8 for ; Fri, 24 Feb 2023 20:17:24 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229840AbjBXURW (ORCPT ); Fri, 24 Feb 2023 15:17:22 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:44924 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229797AbjBXURS (ORCPT ); Fri, 24 Feb 2023 15:17:18 -0500 Received: from mail-ed1-x52e.google.com (mail-ed1-x52e.google.com [IPv6:2a00:1450:4864:20::52e]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id CD45361EFA for ; Fri, 24 Feb 2023 12:17:09 -0800 (PST) Received: by mail-ed1-x52e.google.com with SMTP id eg37so1774734edb.12 for ; Fri, 24 Feb 2023 12:17:09 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linux-foundation.org; s=google; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=oIjZaVoTVRiYI2EI9MNfmYEqGX+2eYmslPvrV4hb04Y=; b=PNmzsJlYLy+1uKOxvOEqIIXYgWt88eDr+EceyU7mtzyAvlN5COX5huKkWnRJM3He38 SLW8PKiw6XnfBYKZ6DNhjirmDKps4/6eUrx3gFw/GVsGHfzH3B+BLCA2pQ0TWezNZPOv spT1BQ0QU4eREUNc1HOHpnJ4apcNtTyrTrOCo= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=oIjZaVoTVRiYI2EI9MNfmYEqGX+2eYmslPvrV4hb04Y=; b=IpXcPlrckTgZI6S1bNMhu//7+rAH0JdbxjOVDHfqMI4jhisMrmVI5s+fLjzXXo8vlH FUsIVlJ5Ids/8BQ0l+2cQIyyVuNQWxoyFV0L7ts+i52FkHy+lshsmY/yvwHfWuXpUysw Tth1ruMC+Wul4TZSU2O3TsZ4eJgS5rb5Cc4ivWpYMSchX6AEPOgY66oPeOUyn97We1eH hiWV8/20uMESM0pheXSrnvW0bOB2v9D0FjDKPmt+ye2l0n/sLRTE3DZ4Zpii22+eA5vD cWPj3/asWUrUaj1Ba9I0OA3gw+ZinctsEGo3sxH4scyHxM6k8gIkfi+o1L758SOrpkcz R7tA== X-Gm-Message-State: AO0yUKXGlB2UPVmPvoe13uABIOnsqznvapN6YoaSJ2/VnQrxTutLIhOj Ztm0dugANOUoSSHGlg8OZLOOqDVMCXCtgbC6JJfuLA== X-Google-Smtp-Source: AK7set9HJWXdQ2c+zaU9UItzT0gIrewOMKoWhms7lhuSaNecNKUfWJFIG/nBy4CyTe52z7Ngzpt8Jg== X-Received: by 2002:a17:907:206e:b0:8b1:3a8e:232 with SMTP id qp14-20020a170907206e00b008b13a8e0232mr21750012ejb.74.1677269827692; Fri, 24 Feb 2023 12:17:07 -0800 (PST) Received: from mail-ed1-f53.google.com (mail-ed1-f53.google.com. [209.85.208.53]) by smtp.gmail.com with ESMTPSA id ck20-20020a170906c45400b008c95f0ce32esm7705032ejb.3.2023.02.24.12.17.06 for (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Fri, 24 Feb 2023 12:17:07 -0800 (PST) Received: by mail-ed1-f53.google.com with SMTP id ck15so2156424edb.0 for ; Fri, 24 Feb 2023 12:17:06 -0800 (PST) X-Received: by 2002:a17:907:988c:b0:877:747e:f076 with SMTP id ja12-20020a170907988c00b00877747ef076mr11089353ejc.0.1677269826565; Fri, 24 Feb 2023 12:17:06 -0800 (PST) MIME-Version: 1.0 References: <2134430.1677240738@warthog.procyon.org.uk> <2009825.1677229488@warthog.procyon.org.uk> <20230220135225.91b0f28344c01d5306c31230@linux-foundation.org> <2213409.1677249075@warthog.procyon.org.uk> <2385089.1677258941@warthog.procyon.org.uk> <2390711.1677269637@warthog.procyon.org.uk> In-Reply-To: <2390711.1677269637@warthog.procyon.org.uk> From: Linus Torvalds Date: Fri, 24 Feb 2023 12:16:49 -0800 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: [RFC][PATCH] cifs: Fix cifs_writepages_region() To: David Howells Cc: Matthew Wilcox , Steve French , Vishal Moola , Andrew Morton , Jan Kara , Paulo Alcantara , Huang Ying , Baolin Wang , Xin Hao , linux-mm@kvack.org, mm-commits@vger.kernel.org, linux-kernel@vger.kernel.org Content-Type: text/plain; charset="UTF-8" Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, Feb 24, 2023 at 12:14 PM David Howells wrote: > > Then why do we have to wait for PG_writeback to complete? At least for PG_writeback, it's about "the _previous_ dirty write is still under way, but - since PG_dirty is set again - the page has been dirtied since". So we have to start _another_ writeback, because while the current writeback *might* have written the updated data, that is not at all certain or clear. I'm not sure what the fscache rules are. Linus