From mboxrd@z Thu Jan 1 00:00:00 1970 From: Linus Torvalds Subject: Re: [PATCH 17/17] RCU'd vfsmounts Date: Thu, 3 Oct 2013 12:06:04 -0700 Message-ID: References: <20131003105130.GE13318@ZenIV.linux.org.uk> <20131003174439.GG13318@ZenIV.linux.org.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Cc: linux-fsdevel , Linux Kernel Mailing List To: Al Viro Return-path: Received: from mail-vb0-f44.google.com ([209.85.212.44]:53938 "EHLO mail-vb0-f44.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754536Ab3JCTGG (ORCPT ); Thu, 3 Oct 2013 15:06:06 -0400 In-Reply-To: <20131003174439.GG13318@ZenIV.linux.org.uk> Sender: linux-fsdevel-owner@vger.kernel.org List-ID: On Thu, Oct 3, 2013 at 10:44 AM, Al Viro wrote: > > Anyway, I've done nicer variants of that protection for everything except > fuse (hadn't gotten around to it yet); see vfs.git#experimental now: Ok, I did a quick test, and it looks ok here, so looking good for 3.13. However, the new smp_mb() in mntput_no_expire() is quite noticeable in the path lookup stress-test profiles. And I'm not seeing what that allegedly protects against, especially if mnt_ns is NULL (ie all the common important cases). Linus