Received: by 2002:a05:7412:b101:b0:e2:908c:2ebd with SMTP id az1csp3099712rdb; Wed, 15 Nov 2023 23:12:01 -0800 (PST) X-Google-Smtp-Source: AGHT+IEaiM+uuZteaKOxIkT8VBp40GpRpxPEld0ULHtUkoZdwqfDAbiahE+9qTQLxud5wH6f4pES X-Received: by 2002:aa7:8048:0:b0:6be:18a9:8f60 with SMTP id y8-20020aa78048000000b006be18a98f60mr12129166pfm.16.1700118721154; Wed, 15 Nov 2023 23:12:01 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1700118721; cv=none; d=google.com; s=arc-20160816; b=ud1kZ9S3KqA0jRmS3VQCaNbV9HB4F6Q5pwkI7XZHdCe8/Ivucum8kD6W8IGJGMLiP2 70zRbnXAh1jXECsvilzG6s5QuxCjA9H6B+b/YQifq2O1HC4Oe1eyYpUVNR7uyvkHj6pZ Qqdj59GZzRrtuBSCnTSHkCXGaerSfFMpOTQIiRx8z41rZeO8zJT/cfR+8VaVTUdEqUJ0 kVgA8hcrjoI7Onzvhi3Q/YlhfthbuGaNMr+kG9+3yBLwXELKrBFdqOdwNK2NFsAUZZw3 w7RC9Yy4/SPDxc2okk8zJ51q8o3NpHBjDzQD1cfcYXtYpdTYuV07lhkaAqipZJNs6EG/ TE2w== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:to:subject:message-id:date:from:mime-version :dkim-signature; bh=YyYlPJ0DDpeEInnpMb8OrHzvYzKIqqHijPIbsicGglQ=; fh=A3pMOUK00huGibGCZBFsLekFLVbB5hHGKjUNNKwO+5E=; b=bVK+5Jm1XhWEWDpbNplEsm+GqVhOhBYw7Kbrac/jzzJ09x7WzMr+iZbIKlNtwIw6tp jlbfnXD5u1f8zWDWk7c2KAiifkFQ6RmDmEqbH6ApGWKiuzAbtSBZPZ1ueHTRCgXnfoNj 9SbKvAJcbMmIO/Mg/c6rwXPmT7yFYSQ/jTHNOdrn3KwKZ2W9uP2cFGfQo74ujng7+Vf+ JSW08aQLWFWhG6ogBMm2tbfY4hvcZstS6ill4G7/uuhEklarrzLvQlGVO3kqIMTSdxYu Uw0VdeB9k6XHc32fOd8fwzyTdl/r7Ur9lSCw7lMdt175jAdPHsDTjdOLPCEkm2939VHq eHkA== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@gmail.com header.s=20230601 header.b=OVTh52UV; spf=pass (google.com: domain of linux-nfs-owner@vger.kernel.org designates 2620:137:e000::3:3 as permitted sender) smtp.mailfrom=linux-nfs-owner@vger.kernel.org; dmarc=pass (p=NONE sp=QUARANTINE dis=NONE) header.from=gmail.com Return-Path: Received: from lipwig.vger.email (lipwig.vger.email. [2620:137:e000::3:3]) by mx.google.com with ESMTPS id ck27-20020a056a02091b00b005740b4723f9si13302875pgb.811.2023.11.15.23.12.00 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Wed, 15 Nov 2023 23:12:01 -0800 (PST) Received-SPF: pass (google.com: domain of linux-nfs-owner@vger.kernel.org designates 2620:137:e000::3:3 as permitted sender) client-ip=2620:137:e000::3:3; Authentication-Results: mx.google.com; dkim=pass header.i=@gmail.com header.s=20230601 header.b=OVTh52UV; spf=pass (google.com: domain of linux-nfs-owner@vger.kernel.org designates 2620:137:e000::3:3 as permitted sender) smtp.mailfrom=linux-nfs-owner@vger.kernel.org; dmarc=pass (p=NONE sp=QUARANTINE dis=NONE) header.from=gmail.com Received: from out1.vger.email (depot.vger.email [IPv6:2620:137:e000::3:0]) by lipwig.vger.email (Postfix) with ESMTP id E653480E761F; Wed, 15 Nov 2023 23:11:56 -0800 (PST) X-Virus-Status: Clean X-Virus-Scanned: clamav-milter 0.103.11 at lipwig.vger.email Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229638AbjKPHL6 (ORCPT + 99 others); Thu, 16 Nov 2023 02:11:58 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:38956 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229919AbjKPHL5 (ORCPT ); Thu, 16 Nov 2023 02:11:57 -0500 Received: from mail-oi1-x22d.google.com (mail-oi1-x22d.google.com [IPv6:2607:f8b0:4864:20::22d]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id D9CF8199 for ; Wed, 15 Nov 2023 23:11:53 -0800 (PST) Received: by mail-oi1-x22d.google.com with SMTP id 5614622812f47-3b2f28caab9so311475b6e.1 for ; Wed, 15 Nov 2023 23:11:53 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1700118713; x=1700723513; darn=vger.kernel.org; h=to:subject:message-id:date:from:mime-version:from:to:cc:subject :date:message-id:reply-to; bh=YyYlPJ0DDpeEInnpMb8OrHzvYzKIqqHijPIbsicGglQ=; b=OVTh52UVTiay7XhPG0TFIGXpHXnWg52osTOfBpxn6XbmglsmacwRNAYVk3ayUtoaOY 9yhZIXzEVeil5YXIzXKuunmGOHTnxzU04hL2EWMG3ASHSkCSMChnf9NBZeZvW+eIgW9Q biiU/nWDt4oLmmuO9VMkVD+FDrMaF/koZldkvSlrjVOH9dCpdHWcuOkaznCh2TwzZ5ye pRy9CYzGrgf1Ufj+RDTHAXwFt7DwEPXVa8Lef+6CmOuxVsJ++QZEs7KzB78CAQYd69o9 qyP+oXfP0SAcbBxwEae20KLBFbpcyazxrP+k75H/GwzPy1ikYeCYyU8TWvss0RyyYE8v +AnA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1700118713; x=1700723513; h=to:subject:message-id:date:from:mime-version:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=YyYlPJ0DDpeEInnpMb8OrHzvYzKIqqHijPIbsicGglQ=; b=LV0cCgEfCqHO4MjkFANZuHXPEUD1eHE7KMpf9clyuYSABInJyj5Q4c+dFQ/LM/vUfv XUBO1fMV7F3X8eJHI3jb//K6RHgBor1qfxzZRedvzxQBDlm5PGKjDbEGpuTIcEEuUUKd RU08I0FNRU11Cp35WmeNyjyfqKIwsjsgnFoBgMIldsP43FMk9Fux0GFkNIJNLg4avGc+ FdWmJaB7+FZ8l3lFSmFjDWLv5XtmcqL3OhTMEm3Nndv0l6gLNG8CjG7VZZdQ+bl5U4e8 wuq0hhVhuPII4bRplZnVCEVvZMZKF9PTzAGQMvZphs7GMw3z2VcCKU5pssqqBLkxng3y z16A== X-Gm-Message-State: AOJu0Ywo9x/joXHu+IhkaCeVZgBIBuFTwWHLkYtBqU3aiTlt6j0OLYLM xBdbhvtV3IixD3+GY/IoNzQf5lfuvCWfeyfQeq4/ok9kmo4= X-Received: by 2002:a05:6871:a589:b0:1d5:a17e:f62 with SMTP id wd9-20020a056871a58900b001d5a17e0f62mr17500284oab.24.1700118712968; Wed, 15 Nov 2023 23:11:52 -0800 (PST) MIME-Version: 1.0 From: Martin Wege Date: Thu, 16 Nov 2023 08:11:42 +0100 Message-ID: Subject: Does NFSv4 close-to-open consistency work with server "async" mount open? To: Linux NFS Mailing List Content-Type: text/plain; charset="UTF-8" X-Spam-Status: No, score=-0.6 required=5.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,FREEMAIL_FORGED_FROMDOMAIN,FREEMAIL_FROM, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,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 lipwig.vger.email Precedence: bulk List-ID: X-Mailing-List: linux-nfs@vger.kernel.org X-Greylist: Sender passed SPF test, not delayed by milter-greylist-4.6.4 (lipwig.vger.email [0.0.0.0]); Wed, 15 Nov 2023 23:11:57 -0800 (PST) Hello, Does NFSv4 close-to-open consistency on the client work with server "async" mount open? We see several build errors here with parallel GNU Makefile update, where one process writes a file, exists, and the next process doesn't see all data (linker ar: file too short). But if you manually look at it the files are OK, and completely written. What is this? NFSv4 client bug, NFSv4 server bug, admin error (async breaking close-to-open consistency? Also, is close-to-open consistency guaranteed between different NFSv4 clients? Thanks, Martin