Received: by 2002:a05:7412:b10a:b0:f3:1519:9f41 with SMTP id az10csp3050051rdb; Mon, 4 Dec 2023 15:31:52 -0800 (PST) X-Google-Smtp-Source: AGHT+IFRdxSjLTacAiF4pYUKzHYiocHBHpLWzltZOT7yfvQnzu5vynVedp+RwocGrB3dwnTTczNU X-Received: by 2002:a17:906:a219:b0:9e3:f97b:239e with SMTP id r25-20020a170906a21900b009e3f97b239emr450838ejy.29.1701732712184; Mon, 04 Dec 2023 15:31:52 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1701732712; cv=none; d=google.com; s=arc-20160816; b=ayhvCoqu8W9icRkYnzgBymfF1ott7F41n9swz33YqL1T/OMwzOiCiNar40+YTmk06H /FpBkyTPG8DjyVmn/r6MFAQFQ8cH6BZ3KSv9AUiJ+7UdY3HFB23nd2rxFqZWqLt289QP YsHZ6K1KmaUCyV1Xq/tgSDxpPo/AbF2G2H4fqzyOuHOxEp4z2wPN95cvU4gXG5TiksQk a/wZXSFFvS3xlj/4ZFy3xrTEjQcdu6kS+XjwF+WLJNCcfOgyWqJrhAWfHUhk/ms39JYi Xazx4xnUjmGqtiafoF4Kl4eRp+BJOAdzgBK7DuLn4fDfooZr1EQTZsNcPSkDq+wBByfT Bj/w== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=message-id:date:references:in-reply-to:subject:cc:to:from :mime-version:list-unsubscribe:list-subscribe:list-id:precedence :content-transfer-encoding; bh=SptzCSvkzvvv87yqiRUF9OmaRnfJyPbH8/6Ow9ZhyB0=; fh=xSlF3QjRs6KG+VYGxlEYBytfhVWLkvU5KIoVgmFro6Q=; b=SebQNMhKWAEd+3vdOEOVitqvY1Y7PJlOAvteQANsHu+KQljU9m71b5aSlpsw+h81ho YYT4IKcQhwGw2048R5KBzCPtdHTXVguSJxgt32yZr56bBFeC5QX6o9tHDVqZyeRGXUhS IuvAyjUgyb2U3mYR+OKL2uJUFzAHVpJTRBVi3hwYqQB/9lL1y5nbWJ1E8SF0odz53VD+ FPIAFNECgEkMO4g4oxvXDC7GPMOVyPkXzFhKMB0J1kp2KnjkPJXaasnBc1cdu5bKr19g DZwoqPwrGm3GcxXltKyYUtjbrzDmEePe3v/vRrTZvPSLn2mODR+cvv6KgIhKpimdLBJt dY7A== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-nfs+bounces-321-linux.lists.archive=gmail.com@vger.kernel.org designates 2604:1380:4601:e00::3 as permitted sender) smtp.mailfrom="linux-nfs+bounces-321-linux.lists.archive=gmail.com@vger.kernel.org"; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=suse.de Return-Path: Received: from am.mirrors.kernel.org (am.mirrors.kernel.org. [2604:1380:4601:e00::3]) by mx.google.com with ESMTPS id f11-20020a170906138b00b00a0a9047a1a1si4774862ejc.761.2023.12.04.15.31.52 for (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Mon, 04 Dec 2023 15:31:52 -0800 (PST) Received-SPF: pass (google.com: domain of linux-nfs+bounces-321-linux.lists.archive=gmail.com@vger.kernel.org designates 2604:1380:4601:e00::3 as permitted sender) client-ip=2604:1380:4601:e00::3; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-nfs+bounces-321-linux.lists.archive=gmail.com@vger.kernel.org designates 2604:1380:4601:e00::3 as permitted sender) smtp.mailfrom="linux-nfs+bounces-321-linux.lists.archive=gmail.com@vger.kernel.org"; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=suse.de Received: from smtp.subspace.kernel.org (wormhole.subspace.kernel.org [52.25.139.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by am.mirrors.kernel.org (Postfix) with ESMTPS id DF1A51F21203 for ; Mon, 4 Dec 2023 23:31:51 +0000 (UTC) Received: from localhost.localdomain (localhost.localdomain [127.0.0.1]) by smtp.subspace.kernel.org (Postfix) with ESMTP id A2A32225AE; Mon, 4 Dec 2023 23:31:49 +0000 (UTC) X-Original-To: linux-nfs@vger.kernel.org Received: from smtp-out2.suse.de (smtp-out2.suse.de [IPv6:2a07:de40:b251:101:10:150:64:2]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 9751D113 for ; Mon, 4 Dec 2023 15:31:46 -0800 (PST) Received: from imap1.dmz-prg2.suse.org (imap1.dmz-prg2.suse.org [IPv6:2a07:de40:b281:104:10:150:64:97]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by smtp-out2.suse.de (Postfix) with ESMTPS id 1563E1FE7F; Mon, 4 Dec 2023 23:31:45 +0000 (UTC) Received: from imap1.dmz-prg2.suse.org (localhost [127.0.0.1]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by imap1.dmz-prg2.suse.org (Postfix) with ESMTPS id 1613E1398A; Mon, 4 Dec 2023 23:31:43 +0000 (UTC) Received: from dovecot-director2.suse.de ([10.150.64.162]) by imap1.dmz-prg2.suse.org with ESMTPSA id ZphuLV9hbmWQBQAAD6G6ig (envelope-from ); Mon, 04 Dec 2023 23:31:43 +0000 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit Precedence: bulk X-Mailing-List: linux-nfs@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 From: "NeilBrown" To: "Cedric Blancher" Cc: "Linux NFS Mailing List" Subject: Re: PATH_MAX/max symlink length in the NFSv4/v4.1 protocol? In-reply-to: References: Date: Tue, 05 Dec 2023 10:31:40 +1100 Message-id: <170173270053.7109.16328574544196615112@noble.neil.brown.name> X-Spamd-Bar: +++++++++++ Authentication-Results: smtp-out2.suse.de; dkim=none; dmarc=fail reason="No valid SPF, No valid DKIM" header.from=suse.de (policy=none); spf=softfail (smtp-out2.suse.de: 2a07:de40:b281:104:10:150:64:97 is neither permitted nor denied by domain of neilb@suse.de) smtp.mailfrom=neilb@suse.de X-Rspamd-Server: rspamd2 X-Spamd-Result: default: False [11.24 / 50.00]; ARC_NA(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; FROM_HAS_DN(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; FREEMAIL_ENVRCPT(0.00)[gmail.com]; TAGGED_RCPT(0.00)[]; MIME_GOOD(-0.10)[text/plain]; R_SPF_SOFTFAIL(4.60)[~all:c]; RCVD_COUNT_THREE(0.00)[3]; SUBJECT_ENDS_QUESTION(1.00)[]; TO_DN_ALL(0.00)[]; MX_GOOD(-0.01)[]; RCPT_COUNT_TWO(0.00)[2]; NEURAL_SPAM_LONG(3.45)[0.986]; FREEMAIL_TO(0.00)[gmail.com]; FUZZY_BLOCKED(0.00)[rspamd.com]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(2.20)[]; MIME_TRACE(0.00)[0:+]; RCVD_TLS_ALL(0.00)[]; BAYES_HAM(-0.00)[35.06%]; DMARC_POLICY_SOFTFAIL(0.10)[suse.de : No valid SPF, No valid DKIM,none] X-Spam-Score: 11.24 X-Rspamd-Queue-Id: 1563E1FE7F On Mon, 04 Dec 2023, Cedric Blancher wrote: > Good evening! > > Does NFSv4/v4.1 have a limit similar to PATH_MAX? What about > symlinks/reparse points? Is there no limit, or is the limit > configurable, or is the limit >= 4096? See: https://www.rfc-editor.org/rfc/rfc5661 There is no explicit limit. The local filesystem on the server might impose a limit, but the protocol itself does not. The protocol *does* declare that a symlink is valid UTF-8. Linux doesn't enforce this. This might sometimes cause confusion. But the length should not. NeilBrown > > Ced > -- > Cedric Blancher > [https://plus.google.com/u/0/+CedricBlancher/] > Institute Pasteur > >