Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S965057Ab2FHWGu (ORCPT ); Fri, 8 Jun 2012 18:06:50 -0400 Received: from mail-wg0-f44.google.com ([74.125.82.44]:51716 "EHLO mail-wg0-f44.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S964922Ab2FHWGo (ORCPT ); Fri, 8 Jun 2012 18:06:44 -0400 MIME-Version: 1.0 In-Reply-To: <20120608220049.GA18024@otc-wbsnb-06> References: <1339191663-17693-1-git-send-email-kirill.shutemov@linux.intel.com> <20120608220049.GA18024@otc-wbsnb-06> From: Linus Torvalds Date: Fri, 8 Jun 2012 15:06:20 -0700 X-Google-Sender-Auth: rHFluJhVNBqsLJDbi8l-3Mizp8Q Message-ID: Subject: Re: [RFC, PATCH] fs: push rcu_barrier() from deactivate_locked_super() to filesystems To: "Kirill A. Shutemov" Cc: Boaz Harrosh , Tao Ma , Andrew Morton , Nick Piggin , "Dmitry V. Levin" , v9fs-developer@lists.sourceforge.net, linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org, linux-afs@lists.infradead.org, linux-btrfs@vger.kernel.org, ceph-devel@vger.kernel.org, linux-cifs@vger.kernel.org, samba-technical@lists.samba.org, codalist@TELEMANN.coda.cs.cmu.edu, ecryptfs@vger.kernel.org, osd-dev@open-osd.org, linux-ext4@vger.kernel.org, fuse-devel@lists.sourceforge.net, linux-mtd@lists.infradead.org, jfs-discussion@lists.sourceforge.net, logfs@logfs.org, linux-nfs@vger.kernel.org, linux-nilfs@vger.kernel.org, linux-ntfs-dev@lists.sourceforge.net, ocfs2-devel@oss.oracle.com, reiserfs-devel@vger.kernel.org Content-Type: text/plain; charset=ISO-8859-1 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 890 Lines: 24 On Fri, Jun 8, 2012 at 3:00 PM, Kirill A. Shutemov wrote: > > IIUC, moving rcu_barrier() up should help, but I can't say that I fully > understand SLAB_DESTROY_BY_RCU semantics. .. hmm. I think you may be right. Even if we do move it up, we probably shouldn't use it. We don't even want SLAB_DESTROY_BY_RCU, since we do the delayed RCU free for other reasons anyway, so it would duplicate the RCU delaying and cause problems. I forgot about that little complication. We could have a separate "RCU_BARRIER_ON_DESTROY" thing, but that's just silly too. Maybe your patch is the right thing. Linus -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/