From mboxrd@z Thu Jan 1 00:00:00 1970 From: Al Viro Subject: Re: [PATCH 17/17] RCU'd vfsmounts Date: Fri, 4 Oct 2013 03:53:51 +0100 Message-ID: <20131004025351.GO13318@ZenIV.linux.org.uk> References: <20131003105130.GE13318@ZenIV.linux.org.uk> <20131003174439.GG13318@ZenIV.linux.org.uk> <20131003194351.GK13318@ZenIV.linux.org.uk> <20131003204142.GL13318@ZenIV.linux.org.uk> <20131003211448.GN13318@ZenIV.linux.org.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: linux-fsdevel , Linux Kernel Mailing List , Christoph Hellwig To: Linus Torvalds Return-path: Content-Disposition: inline In-Reply-To: <20131003211448.GN13318@ZenIV.linux.org.uk> Sender: linux-kernel-owner@vger.kernel.org List-Id: linux-fsdevel.vger.kernel.org On Thu, Oct 03, 2013 at 10:14:48PM +0100, Al Viro wrote: > > So I don't see how they could possibly see ones. Modulo terminal bugs > > in synchronize_barrier() (which can be very slow, but for umount I > > wouldn't worry). Or modulo my brain being fried. > > There's one more place similar to that - kern_unmount(). There we also > go from "longterm vfsmount, mntput() doesn't need to bother checking" > to NULL ->mnt_ns. We can, of course, slap synchronize_rcu() there as > well, but that might make pid_ns and ipc_ns destruction slow... OK, fuse side of things done, smp_mb() in mntput_no_expire() dropped, kern_umount() got synchronize_rcu() (I'm not happy about the last one, but... hell knows; I want to see profiles before deciding what to do about it). Updated branch force-pushed. BTW, brlock defines can go after that; we still two instances of lg_lock, but they spell the primitives out instead of using br_{read,write}_lock aliases. Speaking of those two - I really want to see file_table.c one killed. Christoph, do you have anything along the lines of getting rid of the mark_files_ro() nonsense? After all, a combination of r/w vfsmount and a superblock with MS_RDONLY in flags should do about the right thing these days... I can probably knock something together tomorrow, but you've brought that thing up quite a few times, so if you happen to have a patch more or less ready...