From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <linux-kernel-owner@vger.kernel.org>
Date: Wed, 22 Jun 2016 18:02:57 +0100
From: Al Viro <viro@ZenIV.linux.org.uk>
To: Miklos Szeredi <mszeredi@redhat.com>
Cc: linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH 1/8] vfs: new d_allocate method
Message-ID: <20160622170257.GS14480@ZenIV.linux.org.uk>
References: <1466606110-24297-1-git-send-email-mszeredi@redhat.com>
 <1466606110-24297-2-git-send-email-mszeredi@redhat.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <1466606110-24297-2-git-send-email-mszeredi@redhat.com>
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-fsdevel.vger.kernel.org>

On Wed, Jun 22, 2016 at 04:35:03PM +0200, Miklos Szeredi wrote:
> Allow filesystem to initialize dentry (->d_fsdata to be explicit) at
> allocation time.

Something similar had been discussed a while ago (I don't remember whether
you'd been on Cc, though).  E.g. ceph and lustre would benefit from having
such method (proposed name was ->d_init(), seeing that it's not always
just an allocation).  The subtle part is barriers and I would really like
to see a proof that you don't need any.