Received: by 2002:a05:7412:b101:b0:e2:908c:2ebd with SMTP id az1csp3240161rdb; Thu, 16 Nov 2023 04:30:18 -0800 (PST) X-Google-Smtp-Source: AGHT+IFOBZBoxOoS7fR7P/MM4qnRPowWsnQAs1eAsK5C4IvMPjQdxQtNKSZnFrR06Td4t/S9+PK0 X-Received: by 2002:a05:6a20:8f22:b0:186:4109:a49d with SMTP id b34-20020a056a208f2200b001864109a49dmr13550279pzk.35.1700137818237; Thu, 16 Nov 2023 04:30:18 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1700137818; cv=none; d=google.com; s=arc-20160816; b=UUfHZkhs8/jynPzt+GdpnFQ9RGWSOw2eTdrW4n1WQSTOVITJIcGd5H4OAqsjBVUqSW IH02tXNps9rSvERmwkLOftHYrUlELlH1JvYUS7UOvZB4x/8CAQQCZqQCdXFUvd3WGnUx KwHm5pMDy/lWb8Zv03yQdhuAz7GldHP5/Si8cjO8UcAzrs52fzNFIw1CJLSRngZIr5WK MSRdR0tuH4/cBnFIuItoxcAYVIA1porPnqKKv7WnbU52eVdbFEQth7GrwcibXMh/Pp9C DG1onQl47pWqD/4ZauxJGnwMa4k/qAbSeNOqhySMV+TCD7MreEpWyH3ag6XKBdShnEVx /Vnw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:mime-version:references:in-reply-to:message-id :date:subject:cc:to:from:dkim-signature; bh=vHqjvMiU4Zn1b5ADn/ffz6ZK8IxbKrqjpsxEnn6yJCE=; fh=sNPrBjA++yHSLwvfVTpITizLEq/w9O7gi5qJ/WgO1Ko=; b=e9FDBXhezynsqkKrzsDvJJ8LbRXK7M3JuSGPdpoQeTuaneiEzMT5DuKe2LzpMtpi1K RPgPOhkp6mtg2R/FNd0LdWBu+96S+D6sEAcqEf2Lz9LVK3/Pe29xPFEWrZoiHRFyc1/9 C/2K8R7lHxWtMT7sUoE1QzgptKjXfFIhgy8WugCDMLmib6dOof0jnlcPRhGodSGLCh4e JRkaGnmjpGNUJ0RF+A9E2QldrYnXnLthkdte2yYj7rih1KuptjkAuAKpFy37hdpoevSB wD68Nn0iUoV970IjseloMJO46KE4p8By+TYK1kxEkooUOA+IQbDTtUTLo7htK84ZNPeZ QqOQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=Cb2x1Nz5; spf=pass (google.com: domain of linux-nfs-owner@vger.kernel.org designates 23.128.96.33 as permitted sender) smtp.mailfrom=linux-nfs-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=redhat.com Return-Path: Received: from lipwig.vger.email (lipwig.vger.email. [23.128.96.33]) by mx.google.com with ESMTPS id bw28-20020a056a02049c00b005b98a7d2545si13695007pgb.527.2023.11.16.04.30.17 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Thu, 16 Nov 2023 04:30:18 -0800 (PST) Received-SPF: pass (google.com: domain of linux-nfs-owner@vger.kernel.org designates 23.128.96.33 as permitted sender) client-ip=23.128.96.33; Authentication-Results: mx.google.com; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=Cb2x1Nz5; spf=pass (google.com: domain of linux-nfs-owner@vger.kernel.org designates 23.128.96.33 as permitted sender) smtp.mailfrom=linux-nfs-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=redhat.com Received: from out1.vger.email (depot.vger.email [IPv6:2620:137:e000::3:0]) by lipwig.vger.email (Postfix) with ESMTP id 93914807D697; Thu, 16 Nov 2023 04:30:13 -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 S230374AbjKPMaO (ORCPT + 99 others); Thu, 16 Nov 2023 07:30:14 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:41438 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S230160AbjKPMaO (ORCPT ); Thu, 16 Nov 2023 07:30:14 -0500 Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.129.124]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 89A22DD for ; Thu, 16 Nov 2023 04:30:11 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1700137810; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=vHqjvMiU4Zn1b5ADn/ffz6ZK8IxbKrqjpsxEnn6yJCE=; b=Cb2x1Nz56CvQEa5ukmEBxFMyqw/e0pRJbTUKM+7zXdfG7jV8stFU2//dFGgPgcxOpnqZHA sTOypiV/RGdqbRwjQDlOEFHj1pbXUR2C7lq8vFXNo11V/6N7RvZh+Uhn3V6SoFYdghvNzY XYDB9a1v5ZUTTgekD0ZgFlDS8Y4xOZg= Received: from mimecast-mx02.redhat.com (mimecast-mx02.redhat.com [66.187.233.88]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.3, cipher=TLS_AES_256_GCM_SHA384) id us-mta-15-_IVBHS8VN0yqq-lphjJHNQ-1; Thu, 16 Nov 2023 07:30:07 -0500 X-MC-Unique: _IVBHS8VN0yqq-lphjJHNQ-1 Received: from smtp.corp.redhat.com (int-mx10.intmail.prod.int.rdu2.redhat.com [10.11.54.10]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by mimecast-mx02.redhat.com (Postfix) with ESMTPS id B0418101A54C; Thu, 16 Nov 2023 12:30:06 +0000 (UTC) Received: from [100.85.132.103] (unknown [10.22.48.5]) by smtp.corp.redhat.com (Postfix) with ESMTPS id 4128F492BFD; Thu, 16 Nov 2023 12:30:06 +0000 (UTC) From: Benjamin Coddington To: Martin Wege Cc: Linux NFS Mailing List Subject: Re: Does NFSv4 close-to-open consistency work with server "async" mount open? Date: Thu, 16 Nov 2023 07:30:04 -0500 Message-ID: <08A8C65F-5755-41DC-B29A-DE168B23C968@redhat.com> In-Reply-To: References: MIME-Version: 1.0 Content-Type: text/plain X-Scanned-By: MIMEDefang 3.4.1 on 10.11.54.10 X-Spam-Status: No, score=-1.0 required=5.0 tests=DKIMWL_WL_HIGH,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,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]); Thu, 16 Nov 2023 04:30:14 -0800 (PST) On 16 Nov 2023, at 2:11, Martin Wege wrote: > Hello, > > Does NFSv4 close-to-open consistency on the client work with server > "async" mount open? Yes, I believe it should, but I am looking at knfsd code and I think it won't. > 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? Hard to say, a wire capture would show. My guess is that the server's "async" disables the write gather in nfsd_vfs_write(). > Also, is close-to-open consistency guaranteed between different NFSv4 clients? Yes. Ben