From: Luis de Bethencourt <luisbg@osg.samsung.com>
To: linux-fsdevel@vger.kernel.org
Cc: Richard Weinberger <richard@nod.at>, linux-nfs@vger.kernel.org
Subject: When is export_operations.get_parent triggered?
Date: Sat, 05 Nov 2016 12:59:28 +0000 [thread overview]
Message-ID: <581DD7B0.8080906@osg.samsung.com> (raw)
Hi all,
I recently played with adding the basics to make befs exportable via NFS [0].
I want to implement the get_parent member of the export_operations struct as
well, but I can't seem to trigger this member being called. I have implemented
a solution which I feel is wrong [1], but want to be able to test it before
moving forward.
When is this member triggered? Any advice?
Thanks,
Luis
[0] https://lkml.org/lkml/2016/11/5/40
[1] https://github.com/luisbg/linux-befs/commit/a7d92c746469f1bd60dd1c905587915ecf9884f5
next reply other threads:[~2016-11-05 12:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-05 12:59 Luis de Bethencourt [this message]
2016-11-05 22:03 ` When is export_operations.get_parent triggered? NeilBrown
2016-11-06 12:24 ` Luis de Bethencourt
2016-11-07 17:34 ` J. Bruce Fields
2016-11-08 15:49 ` Luis de Bethencourt
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=581DD7B0.8080906@osg.samsung.com \
--to=luisbg@osg.samsung.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=richard@nod.at \
/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