From: Christian Brauner <brauner@kernel.org>
Date: Wed, 18 Oct 2023 10:26:20 +0000 (+0200)
Subject: porting: update locking requirements
X-Git-Tag: microblaze-v6.8~213^2
X-Git-Url: http://git.monstr.eu/?a=commitdiff_plain;h=5aa9130acb98bacacc8bd9f1489a9269430d0eb8;p=linux-2.6-microblaze.git

porting: update locking requirements

Now that s_umount is never taken under open_mutex update the
documentation to say so.

Link: https://lore.kernel.org/r/20231017184823.1383356-1-hch@lst.de
Signed-off-by: Christian Brauner <brauner@kernel.org>
---

diff --git a/Documentation/filesystems/porting.rst b/Documentation/filesystems/porting.rst
index 4d05b9862451..d69f59700a23 100644
--- a/Documentation/filesystems/porting.rst
+++ b/Documentation/filesystems/porting.rst
@@ -1045,3 +1045,10 @@ filesystem type is now moved to a later point when the devices are closed:
 As this is a VFS level change it has no practical consequences for filesystems
 other than that all of them must use one of the provided kill_litter_super(),
 kill_anon_super(), or kill_block_super() helpers.
+
+---
+
+**mandatory**
+
+Lock ordering has been changed so that s_umount ranks above open_mutex again.
+All places where s_umount was taken under open_mutex have been fixed up.