[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <736635494.1055379.1483509211858.open-xchange@webmail.nmp.proximus.be>
Date: Wed, 4 Jan 2017 06:53:31 +0100 (CET)
From: Fabian Frederick <fabf@...net.be>
To: Al Viro <viro@...IV.linux.org.uk>
Cc: Andrew Morton <akpm@...ux-foundation.org>,
linux-kernel@...r.kernel.org, Jan Kara <jack@...e.cz>,
linux-fsdevel@...r.kernel.org
Subject: Re: [PATCH 3/6 linux-next] fs/affs: make affs exportable
> On 03 January 2017 at 23:29 Al Viro <viro@...IV.linux.org.uk> wrote:
>
>
> On Tue, Jan 03, 2017 at 10:30:39PM +0100, Fabian Frederick wrote:
> > Add standard functions making AFFS work with NFS.
> >
> > Functions based on ext4 implementation.
> > Tested on loop device.
>
> How the hell is that supposed to work with cold dcache? You don't have
> ->get_parent() there at all...
>
> There *IS* a reference to parent directory in those suckers - not the same
> kind as in normal unix filesystems (".." is not a directory entry there -
> it's all fake), but it's doable. be32_to_cpu(AFFS_TAIL(sb, bh)->parent)
> would be the inumber you need, where bh is the inode block of directory.
>
> So it can be done, but not in this form. NAK for the time being...
I worked on that function declared optional in
Documentation/filesystems/nfs/Exporting
but was unable to test it.
Regards,
Fabian
Powered by blists - more mailing lists