From: Christoph Hellwig <hch@infradead.org>
To: hooanon05@yahoo.co.jp
Cc: Christoph Hellwig <hch@infradead.org>,
linux-kernel@vger.kernel.org, greg@kroah.com,
linux-fsdevel@vger.kernel.org
Subject: Re: [RFC Aufs2 #5 28/29] export lookup functions
Date: Fri, 10 Apr 2009 12:54:01 -0400 [thread overview]
Message-ID: <20090410165401.GA20673@infradead.org> (raw)
In-Reply-To: <7612.1239382035@jrobl>
On Sat, Apr 11, 2009 at 01:47:15AM +0900, hooanon05@yahoo.co.jp wrote:
>
> Christoph Hellwig:
> > Strong NACK to all these exports, no one has any buesiness looking at
> > these.
>
> Will you tell me why?
> If you have ever discussed exporting lookup_hash(), then please tell me
> its URL or something.
>
> lookup_hash is necessary for aufs since,
All these are vfs-internal bits, and there is no way we are going to
export them. aufs does a lot of really weird things like this because
it's doing things in a filesystem that should be done in the VFS.
Just making sure these exports aren't going to accidentally put in if
Greg happens to suck this pile into the staging tree.
next prev parent reply other threads:[~2009-04-10 16:54 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-10 7:02 [RFC Aufs2 #5 00/29] souce files J. R. Okajima
2009-04-10 7:02 ` [RFC Aufs2 #5 01/29] aufs documents J. R. Okajima
2009-04-10 7:02 ` [RFC Aufs2 #5 02/29] aufs module global J. R. Okajima
2009-04-10 7:02 ` [RFC Aufs2 #5 03/29] aufs super_block J. R. Okajima
2009-04-10 7:02 ` [RFC Aufs2 #5 04/29] aufs branch directory/filesystem J. R. Okajima
2009-04-10 7:02 ` [RFC Aufs2 #5 05/29] aufs xino J. R. Okajima
2009-04-10 7:02 ` [RFC Aufs2 #5 06/29] aufs object lifetime management via sysfs J. R. Okajima
2009-04-10 7:02 ` [RFC Aufs2 #5 07/29] aufs mount options/flags J. R. Okajima
2009-04-10 7:02 ` [RFC Aufs2 #5 08/29] aufs workqueue J. R. Okajima
2009-04-10 7:02 ` [RFC Aufs2 #5 09/29] aufs sub-VFS J. R. Okajima
2009-04-10 7:02 ` [RFC Aufs2 #5 10/29] aufs sub-dcache J. R. Okajima
2009-04-10 7:02 ` [RFC Aufs2 #5 11/29] aufs copy-up J. R. Okajima
2009-04-10 7:02 ` [RFC Aufs2 #5 12/29] aufs whiteout J. R. Okajima
2009-04-10 7:02 ` [RFC Aufs2 #5 13/29] aufs pseudo-link J. R. Okajima
2009-04-10 7:02 ` [RFC Aufs2 #5 14/29] aufs policies to select one among multiple writable branches J. R. Okajima
2009-04-10 7:02 ` [RFC Aufs2 #5 15/29] aufs dentry and lookup J. R. Okajima
2009-04-10 7:02 ` [RFC Aufs2 #5 16/29] aufs file J. R. Okajima
2009-04-10 7:02 ` [RFC Aufs2 #5 17/29] aufs direcotry J. R. Okajima
2009-04-10 7:02 ` [RFC Aufs2 #5 18/29] aufs inode J. R. Okajima
2009-04-10 7:02 ` [RFC Aufs2 #5 19/29] aufs ioctl J. R. Okajima
2009-04-10 7:02 ` [RFC Aufs2 #5 20/29] aufs sysfs entries J. R. Okajima
2009-04-10 7:02 ` [RFC Aufs2 #5 21/29] aufs debugfs entries J. R. Okajima
2009-04-10 7:02 ` [RFC Aufs2 #5 22/29] aufs branch for loopback block device J. R. Okajima
2009-04-10 7:02 ` [RFC Aufs2 #5 23/29] aufs internal inotify J. R. Okajima
2009-04-10 7:02 ` [RFC Aufs2 #5 24/29] aufs test for fstype J. R. Okajima
2009-04-10 7:02 ` [RFC Aufs2 #5 25/29] aufs debug J. R. Okajima
2009-04-10 7:02 ` [RFC Aufs2 #5 26/29] aufs public header file J. R. Okajima
2009-04-10 7:02 ` [RFC Aufs2 #5 27/29] export splice functions J. R. Okajima
2009-04-10 7:02 ` [RFC Aufs2 #5 28/29] export lookup functions J. R. Okajima
2009-04-10 16:28 ` Christoph Hellwig
2009-04-10 16:47 ` hooanon05
2009-04-10 16:54 ` Christoph Hellwig [this message]
2009-04-10 17:03 ` hooanon05
2009-04-10 17:05 ` Christoph Hellwig
2009-04-10 17:26 ` hooanon05
2009-04-10 17:41 ` Christoph Hellwig
2009-04-10 7:02 ` [RFC Aufs2 #5 29/29] kbuild aufs J. R. Okajima
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=20090410165401.GA20673@infradead.org \
--to=hch@infradead.org \
--cc=greg@kroah.com \
--cc=hooanon05@yahoo.co.jp \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).