From: Joe Perches <joe@perches.com>
To: Evgeniy Polyakov <zbr@ioremap.net>
Cc: linux-kernel@vger.kernel.org, greg@kroah.com,
torvalds@linux-foundation.org, akpm@linux-foundation.org,
linux-fsdevel@vger.kernel.org
Subject: Re: [take 3] pohmelfs: call for inclusion
Date: Fri, 16 Mar 2012 06:29:13 -0700 [thread overview]
Message-ID: <1331904553.5406.34.camel@joe2Laptop> (raw)
In-Reply-To: <20120316121829.GA12685@ioremap.net>
On Fri, 2012-03-16 at 16:18 +0400, Evgeniy Polyakov wrote:
> I'm please to announce new and completely rewritten distributed
> filesystem - POHMELFS
Unfortunately, it doesn't compile against -next.
+static int pohmelfs_fill_super(struct super_block *sb, void *data, int silent)
[]
+ sb->s_root = d_alloc_root(&psb->root->vfs_inode);
commit 4f7e69f8eb314b1dd187026cca2bba5245caf75a
Author: Al Viro <viro@zeniv.linux.org.uk>
Date: Sun Feb 12 22:15:47 2012 -0500
vfs: d_alloc_root() gone
all callers converted to d_make_root() by now
Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>
Documentation/filesystems/porting:
[mandatory]
d_alloc_root() is gone, along with a lot of bugs caused by code
misusing it. Replacement: d_make_root(inode). The difference is,
d_make_root() drops the reference to inode if dentry allocation fails.
next prev parent reply other threads:[~2012-03-16 13:29 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-16 12:18 [take 3] pohmelfs: call for inclusion Evgeniy Polyakov
2012-03-16 13:29 ` Joe Perches [this message]
2012-03-16 13:39 ` Evgeniy Polyakov
2012-03-16 13:43 ` Evgeniy Polyakov
2012-03-16 14:12 ` Joe Perches
2012-03-21 20:27 ` Evgeniy Polyakov
2012-03-21 21:02 ` Linus Torvalds
2012-03-21 21:18 ` Al Viro
2012-03-21 21:37 ` Evgeniy Polyakov
2012-03-21 21:54 ` Al Viro
2012-03-21 22:04 ` Evgeniy Polyakov
2012-03-21 22:28 ` Al Viro
2012-03-21 22:40 ` Evgeniy Polyakov
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=1331904553.5406.34.camel@joe2Laptop \
--to=joe@perches.com \
--cc=akpm@linux-foundation.org \
--cc=greg@kroah.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
--cc=zbr@ioremap.net \
/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).