From mboxrd@z Thu Jan  1 00:00:00 1970
From: Andi Kleen <andi@firstfloor.org>
Subject: Re: [patch 1/6] fs: icache RCU free inodes
Date: Wed, 10 Nov 2010 15:47:21 +0100
Message-ID: <20101110144721.GC7205@basil.fritz.box>
References: <20101109124610.GB11477@amd>
 <87lj52pokp.fsf@basil.nowhere.org>
 <20101109213619.GA3246@amd>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Cc: Andi Kleen <andi@firstfloor.org>,
	Al Viro <viro@ZenIV.linux.org.uk>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org
To: Nick Piggin <npiggin@kernel.dk>
Return-path: <linux-kernel-owner@vger.kernel.org>
Content-Disposition: inline
In-Reply-To: <20101109213619.GA3246@amd>
Sender: linux-kernel-owner@vger.kernel.org
List-Id: linux-fsdevel.vger.kernel.org

> It is in the inode_init_once pile, so yes it has to be returned
> to the allocator initialized.

The kmem_cache_create()s in the file systems don't pass constructors
today. So I don't see how this could work reliably.

-Andi