From mboxrd@z Thu Jan 1 00:00:00 1970 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 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.lore.kernel.org (Postfix) with ESMTPS id A5CB5D2ECF7 for ; Tue, 20 Jan 2026 07:44:30 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lists.infradead.org; s=bombadil.20210309; h=Sender: Content-Transfer-Encoding:Content-Type:List-Subscribe:List-Help:List-Post: List-Archive:List-Unsubscribe:List-Id:In-Reply-To:MIME-Version:References: Message-ID:Subject:Cc:To:From:Date:Reply-To:Content-ID:Content-Description: Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID: List-Owner; bh=GyWEapazf7rRXL5+lHeux3ihAubf2zEbyaRXXw1/wsA=; b=QQngXRcw5AXfTR 9fHa/7JVX2yzVsDzYo2rOjCj7PZ/Yi4/dXekSOKrMfXJUakpxV0fLdymgFFS86bi26xXztU7JjgdP HW8EcT6XUIBH7mLL6lV2/seRAKFJ2W/mi8pwXdeFj3rxfqi2KL9gLsaGv+Yqyghcr8FcQwR1jH7+s OPTr1p94ESwJEACDyZp60+EAcU6M909Kfv97xedr2wA1UMstuK7zbh5CYjjdMxp7Y2Kpup63VFQpH wNzXeMOggNOxw4t3WD1AWqv6OzfWNqMA7SJxLHKx+/j+5c4tqArGJX58cnJICenLGcLyHJB2u/n+X o1xGwA5MGapkb+MdLzOA==; Received: from localhost ([::1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.98.2 #2 (Red Hat Linux)) id 1vi6Pd-00000003Ms7-0E2e; Tue, 20 Jan 2026 07:44:29 +0000 Received: from hch by bombadil.infradead.org with local (Exim 4.98.2 #2 (Red Hat Linux)) id 1vi6PX-00000003MrT-17WL; Tue, 20 Jan 2026 07:44:23 +0000 Date: Mon, 19 Jan 2026 23:44:23 -0800 From: Christoph Hellwig To: Jeff Layton Cc: Christian Brauner , Alexander Viro , Chuck Lever , NeilBrown , Olga Kornievskaia , Dai Ngo , Tom Talpey , Amir Goldstein , Hugh Dickins , Baolin Wang , Andrew Morton , Theodore Ts'o , Andreas Dilger , Jan Kara , Gao Xiang , Chao Yu , Yue Hu , Jeffle Xu , Sandeep Dhavale , Hongbo Li , Chunhai Guo , Carlos Maiolino , Ilya Dryomov , Alex Markuze , Viacheslav Dubeyko , Chris Mason , David Sterba , Luis de Bethencourt , Salah Triki , Phillip Lougher , Steve French , Paulo Alcantara , Ronnie Sahlberg , Shyam Prasad N , Bharath SM , Miklos Szeredi , Mike Marshall , Martin Brandenburg , Mark Fasheh , Joel Becker , Joseph Qi , Konstantin Komarov , Ryusuke Konishi , Trond Myklebust , Anna Schumaker , Dave Kleikamp , David Woodhouse , Richard Weinberger , Jan Kara , Andreas Gruenbacher , OGAWA Hirofumi , Jaegeuk Kim , Jonathan Corbet , David Laight , Dave Chinner , Christoph Hellwig , linux-nfs@vger.kernel.org, linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org, linux-mm@kvack.org, linux-ext4@vger.kernel.org, linux-erofs@lists.ozlabs.org, linux-xfs@vger.kernel.org, ceph-devel@vger.kernel.org, linux-btrfs@vger.kernel.org, linux-cifs@vger.kernel.org, samba-technical@lists.samba.org, linux-unionfs@vger.kernel.org, devel@lists.orangefs.org, ocfs2-devel@lists.linux.dev, ntfs3@lists.linux.dev, linux-nilfs@vger.kernel.org, jfs-discussion@lists.sourceforge.net, linux-mtd@lists.infradead.org, gfs2@lists.linux.dev, linux-f2fs-devel@lists.sourceforge.net, linux-doc@vger.kernel.org Subject: Re: [PATCH v2 01/31] Documentation: document EXPORT_OP_NOLOCKS Message-ID: References: <20260119-exportfs-nfsd-v2-0-d93368f903bd@kernel.org> <20260119-exportfs-nfsd-v2-1-d93368f903bd@kernel.org> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: <20260119-exportfs-nfsd-v2-1-d93368f903bd@kernel.org> X-BeenThere: linux-mtd@lists.infradead.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: Linux MTD discussion mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: "linux-mtd" Errors-To: linux-mtd-bounces+linux-mtd=archiver.kernel.org@lists.infradead.org On Mon, Jan 19, 2026 at 11:26:18AM -0500, Jeff Layton wrote: > + EXPORT_OP_NOLOCKS - Disable file locking on this filesystem. Some > + filesystems cannot properly support file locking as implemented by > + nfsd. A case in point is reexport of NFS itself, which can't be done > + safely without coordinating the grace period handling. Other clustered > + and networked filesystems can be problematic here as well. I'm not sure this is very useful. It really needs to document what locking semantics nfs expects, because otherwise no reader will know if they set this or not. ______________________________________________________ Linux MTD discussion mailing list http://lists.infradead.org/mailman/listinfo/linux-mtd/