From mboxrd@z Thu Jan  1 00:00:00 1970
From: Benny Halevy <bhalevy@panasas.com>
Subject: d_obtain_alias
Date: Mon, 16 Feb 2009 19:31:46 +0200
Message-ID: <4999A302.9020007@panasas.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: linux-fsdevel <linux-fsdevel@vger.kernel.org>
To: Christoph Hellwig <hch@infradead.org>
Return-path: <linux-fsdevel-owner@vger.kernel.org>
Received: from gw-ca.panasas.com ([66.104.249.162]:16782 "EHLO
	laguna.int.panasas.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org
	with ESMTP id S1751093AbZBPRbu (ORCPT
	<rfc822;linux-fsdevel@vger.kernel.org>);
	Mon, 16 Feb 2009 12:31:50 -0500
Sender: linux-fsdevel-owner@vger.kernel.org
List-ID: <linux-fsdevel.vger.kernel.org>

Christoph,

I see that in 4ea3ada2955e4519befa98ff55dd62d6dfbd1705,
you declared d_obtain_alias() as EXPORT_SYMBOL_GPL
and that it's supposed to replace d_alloc_anon which
was declared as EXPORT_SYMBOL and thus available to any
loadable module.

Do you consider d_obtain_alias() an internal API?
What exported API non-GPL'ed loadable file systems are
supposed to use now for fh_to_dentry?

Benny