Exporting jffs2 by nfs with kernel 2.6

David Woodhouse dwmw2 at infradead.org
Thu Sep 28 02:43:19 EDT 2006

On Wed, 2006-09-27 at 16:31 +0200, Gregory CLEMENT wrote:
> Hi all,
> On 2.4.18 we managed to export a jffs2 filesystem by nfs.
> Now on 2.6.16 we can't.
> I found 2 problems for it:
> First, changed was made in nfs, and now they test if
> s_export_op is not a void pointer. By dding a pointer on
> this structure (even this structure is void) makes nfs happy.

> If the structure is void nfs use generic function, so for this part
> I think it's ok

Hm, OK. What are the implications of providing _none_ of our own
functions and just using the defaults? Shouldn't we provide at least a
get_parent() function?

By do we need that anyway? I thought we used to just have disconnected
dentries until we happen to find their place in the tree, at which point
we connect them.

> Second, nfs need to identify the filesystem to export. It is done
> either by the device of the filesystem or by a "fsid". I didfn't see any
> filesystem use a "fsid" and I don't know how to use it. So identification
> is made if FS_REQUIRES_DEV is set. The problem was in kernel 2.5.7,
> this flag was removed because "We never really used the block device anyway".
> Do you mind setting this flag again? Or have you a better idea?

I suspect that we should add another export_ops function for get_fsid().


More information about the linux-mtd mailing list