From: Christoph Hellwig <hch@infradead.org>
To: Benny Halevy <bhalevy@panasas.com>
Cc: Christoph Hellwig <hch@infradead.org>,
Andrew Morton <akpm@linux-foundation.org>,
"J. Bruce Fields" <bfields@fieldses.org>,
Trond Myklebust <trond.myklebust@fys.uio.no>,
linux-nfs@vger.kernel.org, linux-fsdevel@vger.kernel.org
Subject: Re: Ping: d_obtain_alias
Date: Sat, 21 Feb 2009 12:40:46 -0500 [thread overview]
Message-ID: <20090221174046.GA27374@infradead.org> (raw)
In-Reply-To: <499FA991.8080909@panasas.com>
All the nfs exported filesystem are tied intimately to the kernel,
so yes, this is an internal export.
Non-GPL filesystem are illegal to distribute anyway, so I don't know why
you even bother.
On Sat, Feb 21, 2009 at 09:13:21AM +0200, Benny Halevy wrote:
> Christoph?
>
> On Feb. 16, 2009, 19:31 +0200, Benny Halevy <bhalevy@panasas.com> wrote:
>
> 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
---end quoted text---
next prev parent reply other threads:[~2009-02-21 17:40 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-21 7:13 Ping: d_obtain_alias Benny Halevy
2009-02-21 17:40 ` Christoph Hellwig [this message]
2009-02-21 8:41 ` Benny Halevy
2009-02-21 19:40 ` Andrew Morton
2009-02-21 19:49 ` Linus Torvalds
2009-02-24 20:11 ` [PATCH] EXPORT_SYMBOL(d_obtain_alias) rather than EXPORT_SYMBOL_GPL Benny Halevy
2009-02-24 21:32 ` Al Viro
2009-02-24 21:36 ` Linus Torvalds
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20090221174046.GA27374@infradead.org \
--to=hch@infradead.org \
--cc=akpm@linux-foundation.org \
--cc=bfields@fieldses.org \
--cc=bhalevy@panasas.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=trond.myklebust@fys.uio.no \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox