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 X-Spam-Level: X-Spam-Status: No, score=-12.3 required=3.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS,INCLUDES_PATCH, MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS,USER_AGENT_SANE_1 autolearn=ham autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id D7FC1C4338F for ; Fri, 20 Aug 2021 14:09:06 +0000 (UTC) Received: from kanga.kvack.org (kanga.kvack.org [205.233.56.17]) by mail.kernel.org (Postfix) with ESMTP id 68E01610E6 for ; Fri, 20 Aug 2021 14:09:06 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.4.1 mail.kernel.org 68E01610E6 Authentication-Results: mail.kernel.org; dmarc=none (p=none dis=none) header.from=fieldses.org Authentication-Results: mail.kernel.org; spf=pass smtp.mailfrom=kvack.org Received: by kanga.kvack.org (Postfix) id 00AE08D0002; Fri, 20 Aug 2021 10:09:06 -0400 (EDT) Received: by kanga.kvack.org (Postfix, from userid 40) id EFCC48D0001; Fri, 20 Aug 2021 10:09:05 -0400 (EDT) X-Delivered-To: int-list-linux-mm@kvack.org Received: by kanga.kvack.org (Postfix, from userid 63042) id DEB638D0002; Fri, 20 Aug 2021 10:09:05 -0400 (EDT) X-Delivered-To: linux-mm@kvack.org Received: from forelay.hostedemail.com (smtprelay0225.hostedemail.com [216.40.44.225]) by kanga.kvack.org (Postfix) with ESMTP id C2F3C8D0001 for ; Fri, 20 Aug 2021 10:09:05 -0400 (EDT) Received: from smtpin01.hostedemail.com (10.5.19.251.rfc1918.com [10.5.19.251]) by forelay03.hostedemail.com (Postfix) with ESMTP id 630F7822F79C for ; Fri, 20 Aug 2021 14:09:05 +0000 (UTC) X-FDA: 78495640650.01.10DC7FC Received: from fieldses.org (fieldses.org [173.255.197.46]) by imf10.hostedemail.com (Postfix) with ESMTP id 95732600198B for ; Fri, 20 Aug 2021 14:09:04 +0000 (UTC) Received: by fieldses.org (Postfix, from userid 2815) id 0D0065BAF; Fri, 20 Aug 2021 10:09:03 -0400 (EDT) DKIM-Filter: OpenDKIM Filter v2.11.0 fieldses.org 0D0065BAF DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fieldses.org; s=default; t=1629468543; bh=wY8RC3nRl8mw74fg4RiQly9sGS6KY5S4e1kT6ficbDo=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=uLNQrICJHtuq70LWUUqRVgWozgalJ08WFOOsOZqBRr7hBYe8itNg2uNRHfsX8hV9w iqbK/sRw2HXqb1WneQoev11t5SeB+7ucMp6ayp/tLrKmxHPhmbqboCVfkuJrHpOG7M yUwi7bYbplF6X0LxX0UaNOAxpOKbsXq8dEkfIV4U= Date: Fri, 20 Aug 2021 10:09:03 -0400 From: "J. Bruce Fields" To: Jeff Layton Cc: torvalds@linux-foundation.org, linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org, ebiederm@xmission.com, david@redhat.com, willy@infradead.org, linux-nfs@vger.kernel.org, viro@zeniv.linux.org.uk, linux-doc@vger.kernel.org, v9fs-developer@lists.sourceforge.net, linux-afs@lists.infradead.org, cluster-devel@redhat.com, ocfs2-devel@oss.oracle.com, linux-mm@kvack.org, akpm@linux-foundation.org, luto@kernel.org, w@1wt.eu, rostedt@goodmis.org Subject: Re: [PATCH v2 0/2] fs: remove support for mandatory locking Message-ID: <20210820140903.GA18096@fieldses.org> References: <20210820135707.171001-1-jlayton@kernel.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20210820135707.171001-1-jlayton@kernel.org> User-Agent: Mutt/1.5.21 (2010-09-15) Authentication-Results: imf10.hostedemail.com; dkim=pass header.d=fieldses.org header.s=default header.b=uLNQrICJ; dmarc=none; spf=pass (imf10.hostedemail.com: domain of bfields@fieldses.org designates 173.255.197.46 as permitted sender) smtp.mailfrom=bfields@fieldses.org X-Stat-Signature: rdphqjcchayipcbpxh38rjegpq5fens1 X-Rspamd-Queue-Id: 95732600198B X-Rspamd-Server: rspam05 X-HE-Tag: 1629468544-627725 X-Bogosity: Ham, tests=bogofilter, spamicity=0.000000, version=1.2.4 Sender: owner-linux-mm@kvack.org Precedence: bulk X-Loop: owner-majordomo@kvack.org List-ID: On Fri, Aug 20, 2021 at 09:57:05AM -0400, Jeff Layton wrote: > The first patch in this series adds a new warning that should pop on > kernels have mandatory locking enabled when someone mounts a filesystem > with -o mand. The second patch removes support for mandatory locking > altogether. > > What I think we probably want to do is apply the first to v5.14 before > it ships and allow the new warning to trickle out into stable kernels. > Then we can merge the second patch in v5.15 to go ahead and remove it. > > Sound like a plan? Sounds good to me.--b. > > Jeff Layton (2): > fs: warn about impending deprecation of mandatory locks > fs: remove mandatory file locking support > > .../filesystems/mandatory-locking.rst | 188 ------------------ > fs/9p/vfs_file.c | 12 -- > fs/Kconfig | 10 - > fs/afs/flock.c | 4 - > fs/ceph/locks.c | 3 - > fs/gfs2/file.c | 3 - > fs/locks.c | 116 +---------- > fs/namei.c | 4 +- > fs/namespace.c | 31 +-- > fs/nfs/file.c | 4 - > fs/nfsd/nfs4state.c | 13 -- > fs/nfsd/vfs.c | 15 -- > fs/ocfs2/locks.c | 4 - > fs/open.c | 8 +- > fs/read_write.c | 7 - > fs/remap_range.c | 10 - > include/linux/fs.h | 84 -------- > mm/mmap.c | 6 - > mm/nommu.c | 3 - > 19 files changed, 20 insertions(+), 505 deletions(-) > delete mode 100644 Documentation/filesystems/mandatory-locking.rst > > -- > 2.31.1