[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Pine.LNX.4.64.1201101732330.15859@cobra.newdream.net>
Date: Tue, 10 Jan 2012 17:35:36 -0800 (PST)
From: Sage Weil <sage@...dream.net>
To: Al Viro <viro@...IV.linux.org.uk>
cc: Stephen Rothwell <sfr@...b.auug.org.au>,
linux-next@...r.kernel.org, linux-kernel@...r.kernel.org,
Alex Elder <elder@...amhost.com>
Subject: Re: linux-next: manual merge of the ceph tree with Linus' tree
On Wed, 11 Jan 2012, Al Viro wrote:
> On Wed, Jan 11, 2012 at 12:27:44PM +1100, Stephen Rothwell wrote:
> > Hi Sage,
> >
> > Today's linux-next merge of the ceph tree got a conflict in
> > fs/ceph/super.c between commit 3c5184ef1216 ("ceph: d_alloc_root() may
> > fail") from Linus' tree and commit 26d913cdd955 ("ceph: always initialize
> > the dentry in open_root_dentry()") from the ceph tree.
> >
> > I fixed it up (see below) and can carry the fix as necessary.
>
> Ahem...
>
> > + root = d_obtain_alias(inode);
> > + }
> > + ceph_init_dentry(root);
>
> What will happen if dentry returned by d_obtain_alias() had already existed?
ceph_init_dentry() bails out immediately if d_fsdata is non-NULL.
BTW, should I let Linus resolve this, or merge his master back into my
tree, or rebase onto his master?
sage
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists