Received: by 2002:a05:6a10:6d10:0:0:0:0 with SMTP id gq16csp322988pxb; Wed, 20 Apr 2022 23:56:08 -0700 (PDT) X-Google-Smtp-Source: ABdhPJwsGkYMiPMkVBwqmazMK2CyqfwH2ocKJlZ+TGCQjJnL+pr0mNe0WVrgU1gfT334Yo8VqIn+ X-Received: by 2002:a05:6402:1d4b:b0:416:13bf:4fc5 with SMTP id dz11-20020a0564021d4b00b0041613bf4fc5mr23599545edb.115.1650524168668; Wed, 20 Apr 2022 23:56:08 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1650524168; cv=none; d=google.com; s=arc-20160816; b=Wm1NWd3C78qaf64oee9LlA4PhuVi2AmAGmnew/ilK8Dr+dgmV1us4Bc1kcZwaNZtpO Q2VmfeOLkWSswUvMSrX7RV6LCNGXXn60UeK/+zLky3M6T9+dZMnbDcuVHn0aPXsw6gp2 HzL81GuNwWd2NtSclmBUsj0JoLt8NY3Q9n5u2Oy9WqXfiWTe8h559t32uX1mr9tAA96L xws6jX9GDSOWWGyDFlnUVEm/a4qEoXzHJj1c0Lii7/uJp1QIe2V/cZV00psskpZFFhN5 57RV49r8PMMJJzDW9HFLnpxgFBmINVq9vK8OgLb4DWxvyS3tqM0NLohTLGRfTXKYKiwb PyYg== 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; bh=W17F1X3yWK6nfjjnrJO2pr/Y65LG5rz/D4wHcUexup8=; b=gM5pacUozu5mgttvgcjtXkx46mt7aFe5+SckgmZN5qgFm+kkxGoPv2RbZZovY63Tpk GTKoWOJAVj8meZdXUU8t5lB7iwhB8AA3nO7sGCcFASjjw6l7mLZIFx60P+z5RRSZe6zT elBHWyRDDNGAWxQYDKUo+CW2phBsk78gj/I+dRC0igslznCSuTCWls0VO0XwVfetDJCj dPlFRE2jP1nzZtRCNp/h0Ft0+rED9S7MV3dsype696XvoizIGoUV6UjphP9vHPqG8yI5 GJ/Rd3dRGZdk3Zf3ncFr2zHy6XtPvsro/S8EIb9wpEwKvDuOoFBXyJpZUbDCPcXScBM+ 3hhA== ARC-Authentication-Results: i=1; mx.google.com; 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 Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id u24-20020aa7d0d8000000b00423ef0daa6asi3128072edo.327.2022.04.20.23.55.45; Wed, 20 Apr 2022 23:56:08 -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; 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 Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S238961AbiDSSEr (ORCPT + 99 others); Tue, 19 Apr 2022 14:04:47 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:43560 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S239074AbiDSSEo (ORCPT ); Tue, 19 Apr 2022 14:04:44 -0400 Received: from nibbler.cm4all.net (nibbler.cm4all.net [IPv6:2001:8d8:970:e500:82:165:145:151]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id C50D63B3EC for ; Tue, 19 Apr 2022 11:02:00 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by nibbler.cm4all.net (Postfix) with ESMTP id 42AF5C00E1 for ; Tue, 19 Apr 2022 20:01:59 +0200 (CEST) X-Virus-Scanned: Debian amavisd-new at nibbler.cm4all.net Received: from nibbler.cm4all.net ([127.0.0.1]) by localhost (nibbler.cm4all.net [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 1UwKaoVAu4mX for ; Tue, 19 Apr 2022 20:01:52 +0200 (CEST) Received: from zero.intern.cm-ag (zero.intern.cm-ag [172.30.16.10]) by nibbler.cm4all.net (Postfix) with SMTP id 266D3C00DA for ; Tue, 19 Apr 2022 20:01:52 +0200 (CEST) Received: (qmail 2504 invoked from network); 19 Apr 2022 23:51:54 +0200 Received: from unknown (HELO rabbit.intern.cm-ag) (172.30.3.1) by zero.intern.cm-ag with SMTP; 19 Apr 2022 23:51:54 +0200 Received: by rabbit.intern.cm-ag (Postfix, from userid 1023) id E6D21460F1C; Tue, 19 Apr 2022 20:01:51 +0200 (CEST) Date: Tue, 19 Apr 2022 20:01:51 +0200 From: Max Kellermann To: David Howells Cc: Max Kellermann , linux-cachefs@redhat.com, linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: fscache corruption in Linux 5.17? Message-ID: References: <507518.1650383808@warthog.procyon.org.uk> <509961.1650386569@warthog.procyon.org.uk> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <509961.1650386569@warthog.procyon.org.uk> X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00,SPF_HELO_NONE, SPF_PASS,T_SCC_BODY_TEXT_LINE autolearn=unavailable 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 On 2022/04/19 18:42, David Howells wrote: > Could the file have been modified by a third party? According to our support tickets, the customers used WordPress's built-in updater, which resulted in corrupt PHP sources. We have configured stickiness in the load balancer; HTTP requests to one website always go through the same web server. Which implies that the same web server that saw the corrupt files was the very same one that wrote the new file contents. This part surprises me, because writing a page to the NFS server should update (or flush/invalidate) the old cache page. It would be easy for a *different* NFS client to miss out on updated file contents, but this is not what happened. On 2022/04/19 18:47, David Howells wrote: > Do the NFS servers change the files that are being served - or is it > just WordPress pushing the changes to the NFS servers for the web > servers to then export? I'm not sure if I understand this question correctly. The NFS server (a NetApp, btw.) sees the new file contents correctly; all other web servers also see non-corrupt new files. Only the one web server which performed the update saw broken files. Max