From patchwork Mon Jan 23 16:58:47 2023 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: David Wysochanski X-Patchwork-Id: 13112577 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 1582BC05027 for ; Mon, 23 Jan 2023 16:59:37 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S231547AbjAWQ7g (ORCPT ); Mon, 23 Jan 2023 11:59:36 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:37224 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S230231AbjAWQ7f (ORCPT ); Mon, 23 Jan 2023 11:59:35 -0500 Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.133.124]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 7C14F10C8 for ; Mon, 23 Jan 2023 08:58:51 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1674493130; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=3az8ZLlcg0zFGzRORWOiXbm95QueTQ9J9aLCyFL+kWw=; b=VedzLXyG+myXH1f4+NjfHZas3oWdCNUYCh+XKHgQMbWXk2ukEGN7Vt8Mg7OX0Rx7qs9bRe Q41cxUFOTCYtIe2u2olq1+d8wiOghZM5kSr7PMruN0DL3tW6K/pEu6Q0T+EpoLdGtMFSkA 0aqRccYlJtz0yPsCCLF5D4vZPsFP550= Received: from mimecast-mx02.redhat.com (mimecast-mx02.redhat.com [66.187.233.88]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id us-mta-388-30911d7yPOOj6xCfjD-C2A-1; Mon, 23 Jan 2023 11:58:49 -0500 X-MC-Unique: 30911d7yPOOj6xCfjD-C2A-1 Received: from smtp.corp.redhat.com (int-mx05.intmail.prod.int.rdu2.redhat.com [10.11.54.5]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx02.redhat.com (Postfix) with ESMTPS id 09BA287A9E0; Mon, 23 Jan 2023 16:58:49 +0000 (UTC) Received: from dwysocha.rdu.csb (unknown [10.22.16.59]) by smtp.corp.redhat.com (Postfix) with ESMTPS id DAD27175A2; Mon, 23 Jan 2023 16:58:48 +0000 (UTC) From: Dave Wysochanski To: Anna Schumaker Cc: Chuck Lever III , linux-nfs@vger.kernel.org Subject: [PATCH] Documentation: Fix sysfs path for the NFSv4 client identifier Date: Mon, 23 Jan 2023 11:58:47 -0500 Message-Id: <20230123165847.1829613-1-dwysocha@redhat.com> In-Reply-To: <0429A14B-2065-4B6D-8B48-8535AD05A15A@oracle.com> References: <0429A14B-2065-4B6D-8B48-8535AD05A15A@oracle.com> MIME-Version: 1.0 X-Scanned-By: MIMEDefang 3.1 on 10.11.54.5 Precedence: bulk List-ID: X-Mailing-List: linux-nfs@vger.kernel.org The sysfs path for the NFS4 client identfier should start with the path component of 'nfs' for the kset, and then the 'net' path component for the netns object, followed by the 'nfs_client' path component for the NFS client kobject, and ending with 'identifier' for the netns_client_id kobj_attribute. Fixes: a28faaddb2be ("Documentation: Add an explanation of NFSv4 client identifiers") Link: https://bugzilla.redhat.com/show_bug.cgi?id=1801326 Reviewed-by: Chuck Lever Signed-off-by: Dave Wysochanski --- Documentation/filesystems/nfs/client-identifier.rst | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/Documentation/filesystems/nfs/client-identifier.rst b/Documentation/filesystems/nfs/client-identifier.rst index 5147e15815a1..a94c7a9748d7 100644 --- a/Documentation/filesystems/nfs/client-identifier.rst +++ b/Documentation/filesystems/nfs/client-identifier.rst @@ -152,7 +152,7 @@ string: via the kernel command line, or when the "nfs" module is loaded. - /sys/fs/nfs/client/net/identifier + /sys/fs/nfs/net/nfs_client/identifier This virtual file, available since Linux 5.3, is local to the network namespace in which it is accessed and so can provide distinction between network namespaces (containers) when the @@ -164,7 +164,7 @@ then that uniquifier can be used. For example, a uniquifier might be formed at boot using the container's internal identifier: sha256sum /etc/machine-id | awk '{print $1}' \\ - > /sys/fs/nfs/client/net/identifier + > /sys/fs/nfs/net/nfs_client/identifier Security considerations -----------------------