From mboxrd@z Thu Jan 1 00:00:00 1970 From: Christoph Hellwig Subject: Re: [PATCH 17/17] RCU'd vfsmounts Date: Fri, 4 Oct 2013 10:37:29 +0200 Message-ID: <20131004083729.GA23116@lst.de> 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> <20131004025351.GO13318@ZenIV.linux.org.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: Linus Torvalds , linux-fsdevel , Linux Kernel Mailing List , Christoph Hellwig To: Al Viro Return-path: Content-Disposition: inline In-Reply-To: <20131004025351.GO13318@ZenIV.linux.org.uk> Sender: linux-kernel-owner@vger.kernel.org List-Id: linux-fsdevel.vger.kernel.org On Fri, Oct 04, 2013 at 03:53:51AM +0100, Al Viro wrote: > 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... I used to have a patch for it that was also sent to the list long ago, but it got rid of the sysrq emergency remount r/o, which people didn't like.