summaryrefslogtreecommitdiff
path: root/fs/namespace.c
diff options
context:
space:
mode:
authorChristian Brauner <brauner@kernel.org>2024-12-19 14:59:14 +0100
committerChristian Brauner <brauner@kernel.org>2025-01-09 16:58:55 +0100
commit22eb23b8a7b2536a475ac87244ee4ab50764eccd (patch)
treecfaea87d2be106f3cd3f7de20c7c06cd0feb0981 /fs/namespace.c
parent7f9bfafc5f496cf2222659890477d0408455369e (diff)
fs: remove useless lockdep assertion
mnt_ns_release() can run asynchronously via call_rcu() so hitting that lockdep assertion means someone else already grabbed the mnt_ns_tree_lock and causes a false positive. That assertion has likely always been wrong. call_rcu() just makes it more likely to hit. Link: https://lore.kernel.org/r/Z2PlT5rcRTIhCpft@ly-workstation Link: https://lore.kernel.org/r/20241219-darben-quietschen-b6e1d80327bb@brauner Reported-by: Lai, Yi <yi1.lai@linux.intel.com> Signed-off-by: Christian Brauner <brauner@kernel.org>
Diffstat (limited to 'fs/namespace.c')
-rw-r--r--fs/namespace.c2
1 files changed, 0 insertions, 2 deletions
diff --git a/fs/namespace.c b/fs/namespace.c
index e607762fd9c7..371c860f49de 100644
--- a/fs/namespace.c
+++ b/fs/namespace.c
@@ -160,8 +160,6 @@ static void mnt_ns_tree_add(struct mnt_namespace *ns)
static void mnt_ns_release(struct mnt_namespace *ns)
{
- lockdep_assert_not_held(&mnt_ns_tree_lock.lock);
-
/* keep alive for {list,stat}mount() */
if (refcount_dec_and_test(&ns->passive)) {
put_user_ns(ns->user_ns);