All of lore.kernel.org
 help / color / mirror / Atom feed
From: Lucas Karpinski <lkarpins@redhat.com>
To: viro@zeniv.linux.org.uk, brauner@kernel.org, jack@suse.cz
Cc: raven@themaw.net, linux-fsdevel@vger.kernel.org,
	linux-kernel@vger.kernel.org,
	Lucas Karpinski <lkarpins@redhat.com>
Subject: [RFC v3 0/1] fs/namespace: defer RCU sync for MNT_DETACH umount
Date: Wed, 26 Jun 2024 16:07:48 -0400	[thread overview]
Message-ID: <20240626201129.272750-2-lkarpins@redhat.com> (raw)

Hi all,                                            
                                                   
Attached is v3 of the umount optimization. Please take a look at v1 for
the original introduction to the problem. Al made it clear in the
RFC v1 that if a filesystem is shut down by umount(2), that the
shut down needs to be completed before the return from the syscall. In 
the RFC v2, it was pointed out that call_rcu can block within an 
interrupt context. This RFC v3 addresses both that and removes 
unneccesary code by taking advantage of mntput for the cleanup of lazy 
umounts.                                           
                                                   
Lucas                                              
                                                   
v3:                                                
- Removed unneeded code for lazy umount case.      
- Don't block within interrupt context.            
v2:                                                
- Only defer releasing umount'ed filesystems for lazy umounts
v1:                                                
https://lore.kernel.org/all/20230119205521.497401-1-echanude@redhat.com/

Lucas Karpinski (1):
  fs/namespace: remove RCU sync for MNT_DETACH umount

 fs/namespace.c | 9 ++++++++-
 1 file changed, 8 insertions(+), 1 deletion(-)

-- 
2.45.2


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

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-26 20:07 Lucas Karpinski [this message]
2024-06-26 20:07 ` [RFC v3 1/1] fs/namespace: remove RCU sync for MNT_DETACH umount Lucas Karpinski
2024-06-26 20:47   ` Matthew Wilcox
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=20240626201129.272750-2-lkarpins@redhat.com \
    --to=lkarpins@redhat.com \
    --cc=brauner@kernel.org \
    --cc=jack@suse.cz \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --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.