All of lore.kernel.org
 help / color / mirror / Atom feed
From: Matthew Wilcox <willy@infradead.org>
To: Lucas Karpinski <lkarpins@redhat.com>
Cc: viro@zeniv.linux.org.uk, brauner@kernel.org, jack@suse.cz,
	raven@themaw.net, linux-fsdevel@vger.kernel.org,
	linux-kernel@vger.kernel.org,
	Alexander Larsson <alexl@redhat.com>,
	Eric Chanudet <echanude@redhat.com>, Ian Kent <ikent@redhat.com>
Subject: Re: [RFC v3 1/1] fs/namespace: remove RCU sync for MNT_DETACH umount
Date: Wed, 26 Jun 2024 21:47:20 +0100	[thread overview]
Message-ID: <Znx-WGU5Wx6RaJyD@casper.infradead.org> (raw)
In-Reply-To: <20240626201129.272750-3-lkarpins@redhat.com>

On Wed, Jun 26, 2024 at 04:07:49PM -0400, Lucas Karpinski wrote:
> +++ b/fs/namespace.c
> @@ -78,6 +78,7 @@ static struct kmem_cache *mnt_cache __ro_after_init;
>  static DECLARE_RWSEM(namespace_sem);
>  static HLIST_HEAD(unmounted);	/* protected by namespace_sem */
>  static LIST_HEAD(ex_mountpoints); /* protected by namespace_sem */
> +static bool lazy_unlock = false; /* protected by namespace_sem */

That's a pretty ugly way of doing it.  How about this?

+++ b/fs/namespace.c
@@ -1553,7 +1553,7 @@ int may_umount(struct vfsmount *mnt)
 
 EXPORT_SYMBOL(may_umount);
 
-static void namespace_unlock(void)
+static void __namespace_unlock(bool lazy)
 {
        struct hlist_head head;
        struct hlist_node *p;
@@ -1570,7 +1570,8 @@ static void namespace_unlock(void)
        if (likely(hlist_empty(&head)))
                return;
 
-       synchronize_rcu_expedited();
+       if (!lazy)
+               synchronize_rcu_expedited();
 
        hlist_for_each_entry_safe(m, p, &head, mnt_umount) {
                hlist_del(&m->mnt_umount);
@@ -1578,6 +1579,11 @@ static void namespace_unlock(void)
        }
 }
 
+static inline void namespace_unlock(void)
+{
+       __namespace_unlock(false);
+}
+
 static inline void namespace_lock(void)
 {
        down_write(&namespace_sem);
@@ -1798,7 +1804,7 @@ static int do_umount(struct mount *mnt, int flags)
        }
 out:
        unlock_mount_hash();
-       namespace_unlock();
+       __namespace_unlock(flags & MNT_DETACH);
        return retval;
 }
 

(other variants on this theme might be to pass the flags to
__namespace_unlock() and check MNT_DETACH there)

  reply	other threads:[~2024-06-26 20:58 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-26 20:07 [RFC v3 0/1] fs/namespace: defer RCU sync for MNT_DETACH umount Lucas Karpinski
2024-06-26 20:07 ` [RFC v3 1/1] fs/namespace: remove " Lucas Karpinski
2024-06-26 20:47   ` Matthew Wilcox [this message]
2024-06-27  1:11     ` Ian Kent
2024-06-27 11:54       ` Jan Kara
2024-06-27 15:16         ` Christian Brauner
2024-06-28  3:17           ` Ian Kent
2024-06-28 12:54             ` Christian Brauner
2024-06-28 15:13               ` Alexander Larsson
2024-07-01  0:58                 ` Ian Kent
2024-07-01  5:50                   ` Christian Brauner
2024-07-01  8:03                     ` Ian Kent
2024-07-01  8:41                     ` Alexander Larsson
2024-07-01 10:15                       ` Jan Kara
2024-07-01 12:13                         ` Christian Brauner
2024-07-01 12:10                       ` Christian Brauner
2024-07-03  9:22                         ` Christian Brauner
2024-07-04  1:23                           ` Ian Kent
2024-07-02  1:29                     ` Ian Kent
2024-07-02  4:50                       ` Christian Brauner
2024-06-28  2:58         ` Ian Kent
2024-06-28 11:13           ` Jan Kara
2024-07-01  1:08             ` Ian Kent
2024-07-02  4:58             ` Christian Brauner
2024-07-02  7:01               ` Ian Kent
2024-07-02 10:01                 ` Jan Kara

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=Znx-WGU5Wx6RaJyD@casper.infradead.org \
    --to=willy@infradead.org \
    --cc=alexl@redhat.com \
    --cc=brauner@kernel.org \
    --cc=echanude@redhat.com \
    --cc=ikent@redhat.com \
    --cc=jack@suse.cz \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkarpins@redhat.com \
    --cc=raven@themaw.net \
    --cc=viro@zeniv.linux.org.uk \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.