From nobody Mon Apr 6 15:52:17 2026 Received: from bombadil.infradead.org (bombadil.infradead.org [198.137.202.133]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id E590A30BF67; Wed, 18 Mar 2026 22:21:06 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=198.137.202.133 ARC-Seal: i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1773872468; cv=none; b=rxFtVD5VJBP3cDvrS1/U6dmOvvSamzQR8OHO95HzZ+j1q3fjX2uktm9vGCsFiQoJwbeC9YLVLxnNwNTaIOmSTHg43ioukeDfNUjOXRS3nL/2AB4yiro2yMcSuKu3Lnoh4XfmogFT1RQAgqXWZ04QFRsTmWMFEPcxFP2DiM/5q8g= ARC-Message-Signature: i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1773872468; c=relaxed/simple; bh=OXJH/WQXIwljxWLSOn1MCT66uyjPLJ9/bptLdNUiBY8=; h=From:To:Cc:Subject:Date:Message-ID:MIME-Version; b=e7mBYDiwuginfCx2u2FHxLZ3yHT2AURQo1Gp7bZBH4NNMjXLfyhVbC+Vw8fW+6WLUsWacYIwUE3sKpduCg1eqWedJOOUR22NCfEkADsq15teiP/JpTaiAlcwIrjlBnBEhIlkozWpgYd0yryy3IqeKknbvv86E/770QAjbK8XjCU= ARC-Authentication-Results: i=1; smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=infradead.org; spf=none smtp.mailfrom=infradead.org; dkim=pass (2048-bit key) header.d=infradead.org header.i=@infradead.org header.b=iq+zsiSd; arc=none smtp.client-ip=198.137.202.133 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=infradead.org Authentication-Results: smtp.subspace.kernel.org; spf=none smtp.mailfrom=infradead.org Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=infradead.org header.i=@infradead.org header.b="iq+zsiSd" DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=infradead.org; s=bombadil.20210309; h=Content-Transfer-Encoding: MIME-Version:Message-ID:Date:Subject:Cc:To:From:Sender:Reply-To:Content-Type: Content-ID:Content-Description:In-Reply-To:References; bh=A1pzINGI0p7kOYnI6h/PSeamIRgJ4xB+DsKqeGxuT6g=; b=iq+zsiSdjL9/JcAHtVmOVLkqlU 6YXk9ptjNwl7qQEPrH66Byr5HuC+HcuQ/l1+mrGvLdz2QzfXOyLIiYyV6bWNYTsGIxfOgUt59btqo +mNa2KDQWZ2m3eqjmCyoWLxQzWvBhe7xv8p4B84JLu6JIqNO1Fi/PM53Zr+J10KX0BNGLX+ShbuIp T51V5hC2flPD3GRjRf5kHbOeGScCpKMDEt4i7GFggF0YCfzTsc/hbEP8NIMgaYnHs53k5OW/OQ7Tj euUqUKM5rb10HLRmFewYJvfy/0hOp6zMmP/OZALFQD6JG5td2hBJERqTOYWtQY2ckGnyk2bjmvVDw loEkLT1A==; Received: from [50.53.43.113] (helo=bombadil.infradead.org) by bombadil.infradead.org with esmtpsa (Exim 4.98.2 #2 (Red Hat Linux)) id 1w2zGE-00000009Qor-1EsJ; Wed, 18 Mar 2026 22:21:06 +0000 From: Randy Dunlap To: linux-kernel@vger.kernel.org Cc: Randy Dunlap , Dai Ngo , Chuck Lever , linux-nfs@vger.kernel.org, linux-doc@vger.kernel.org Subject: [PATCH] NFSD: Docs: clean up pnfs server timeout docs Date: Wed, 18 Mar 2026 15:21:05 -0700 Message-ID: <20260318222105.3031225-1-rdunlap@infradead.org> X-Mailer: git-send-email 2.53.0 Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="utf-8" Make various changes to the documentation formatting to avoid docs build errors and otherwise improve the produced output format: - use bullets for lists - don't use a '.' at the end of echo commands - fix indentation Documentation/admin-guide/nfs/pnfs-block-server.rst:55: ERROR: Unexpected i= ndentation. [docutils] Documentation/admin-guide/nfs/pnfs-scsi-server.rst:37: ERROR: Unexpected in= dentation. [docutils] Fixes: 6a97f70b45e7 ("NFSD: Enforce timeout on layout recall and integrate = lease manager fencing") Signed-off-by: Randy Dunlap --- # for Chuck's tree Cc: Dai Ngo Cc: Chuck Lever Cc: linux-nfs@vger.kernel.org Cc: linux-doc@vger.kernel.org Documentation/admin-guide/nfs/pnfs-block-server.rst | 20 +++++----- Documentation/admin-guide/nfs/pnfs-scsi-server.rst | 20 +++++----- 2 files changed, 20 insertions(+), 20 deletions(-) --- linux-next-20260316.orig/Documentation/admin-guide/nfs/pnfs-block-serve= r.rst +++ linux-next-20260316/Documentation/admin-guide/nfs/pnfs-block-server.rst @@ -47,12 +47,12 @@ system log with the following format: =20 FENCE failed client[IP_address] clid[#n] device[dev_name] =20 - Where: + where: =20 - IP_address: refers to the IP address of the affected client. - #n: indicates the unique client identifier. - dev_name: specifies the name of the block device related - to the fencing attempt. + - IP_address: refers to the IP address of the affected client. + - #n: indicates the unique client identifier. + - dev_name: specifies the name of the block device related + to the fencing attempt. =20 The server will repeatedly retry the operation indefinitely. During this time, access to the affected file is restricted for all other @@ -62,11 +62,11 @@ clients access the same file simultaneou To restore access to the affected file for other clients, the admin needs to take the following actions: =20 - . shutdown or power off the client being fenced. - . manually expire the client to release all its state on the server: + - shutdown or power off the client being fenced. + - manually expire the client to release all its state on the server:: =20 - echo 'expire' > /proc/fs/nfsd/clients/clid/ctl'. + echo 'expire' > /proc/fs/nfsd/clients/clid/ctl' =20 - Where: + where: =20 - clid: is the unique client identifier displayed in the system log. + - clid: is the unique client identifier displayed in the system log. --- linux-next-20260316.orig/Documentation/admin-guide/nfs/pnfs-scsi-server= .rst +++ linux-next-20260316/Documentation/admin-guide/nfs/pnfs-scsi-server.rst @@ -29,12 +29,12 @@ system log with the following format: =20 FENCE failed client[IP_address] clid[#n] device[dev_name] =20 - Where: + where: =20 - IP_address: refers to the IP address of the affected client. - #n: indicates the unique client identifier. - dev_name: specifies the name of the block device related - to the fencing attempt. + - IP_address: refers to the IP address of the affected client. + - #n: indicates the unique client identifier. + - dev_name: specifies the name of the block device related + to the fencing attempt. =20 The server will repeatedly retry the operation indefinitely. During this time, access to the affected file is restricted for all other @@ -44,12 +44,12 @@ clients access the same file simultaneou To restore access to the affected file for other clients, the admin needs to take the following actions: =20 - . shutdown or power off the client being fenced. - . manually expire the client to release all its state on the server: + - shutdown or power off the client being fenced. + - manually expire the client to release all its state on the server:: =20 - echo 'expire' > /proc/fs/nfsd/clients/clid/ctl'. + echo 'expire' > /proc/fs/nfsd/clients/clid/ctl' =20 - Where: + where: =20 - clid: is the unique client identifier displayed in the system log. + - clid: is the unique client identifier displayed in the system log.