From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752376AbcLDCSn (ORCPT ); Sat, 3 Dec 2016 21:18:43 -0500 Received: from out5-smtp.messagingengine.com ([66.111.4.29]:56310 "EHLO out5-smtp.messagingengine.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752292AbcLDCSl (ORCPT ); Sat, 3 Dec 2016 21:18:41 -0500 X-ME-Sender: X-Sasl-enc: kbzPDfpd0IsUem4ZSEJynbz2A9xrdFFa43CjSh1trMaB 1480817919 Message-ID: <1480817915.3157.14.camel@themaw.net> Subject: Re: [PATCH 1/7] vfs - merge path_is_mountpoint() and path_is_mountpoint_rcu() From: Ian Kent To: Al Viro Cc: Andrew Morton , autofs mailing list , Kernel Mailing List , "Eric W. Biederman" , linux-fsdevel , Omar Sandoval Date: Sun, 04 Dec 2016 10:18:35 +0800 In-Reply-To: <20161203232912.GE1555@ZenIV.linux.org.uk> References: <148029910861.27779.4517883721395202453.stgit@pluto.themaw.net> <20161203051322.GA24765@ZenIV.linux.org.uk> <20161203232912.GE1555@ZenIV.linux.org.uk> Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.18.5.2 (3.18.5.2-1.fc23) Mime-Version: 1.0 Content-Transfer-Encoding: 8bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Sat, 2016-12-03 at 23:29 +0000, Al Viro wrote: > On Sat, Dec 03, 2016 at 05:13:22AM +0000, Al Viro wrote: > > > > * path_has_submounts() is broken.  At the very least, it's > > AB-BA between mount_lock and rename_lock.  I would suggest trying to > > put read_seqlock_excl(&mount_lock) around the call of d_walk() in there, > > and using __lookup_mnt() in the callback (without retries on the mount_lock, > > of course - read_seqlock_excl done on the outside is enough).  I'm not sure > > if it won't cause trouble with contention, though; that needs testing.  As > > it is, that function is broken in #work.autofs, same as it is in -mm and > > -next. > Fix for path_has_submounts() (as above) force-pushed.  It does > need testing and profiling, obviously. I'll run my tests against it and re-run with oprofile if all goes well. The submount-test I use should show contention if it's a problem but I'm not sure the number of mounts used will be sufficient to show up scale problems. Basically each case of the test (there are two) runs for 100 iterations using 10 processes with timing set to promote expire to mount contention, mainly to test for expire to mount races. If I don't see contention I might need to analyse further whether the test has adequate coverage. Ian