From: Nathan Scott <nathans@sgi.com>
To: Jan Engelhardt <jengelh@linux01.gwdg.de>
Cc: linux-xfs@oss.sgi.com,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: xfs depends on exportfs
Date: Wed, 18 Jan 2006 07:42:23 +1100 [thread overview]
Message-ID: <20060118074223.A8500612@wobbly.melbourne.sgi.com> (raw)
In-Reply-To: <Pine.LNX.4.61.0601172112550.11929@yvahk01.tjqt.qr>; from jengelh@linux01.gwdg.de on Tue, Jan 17, 2006 at 09:16:51PM +0100
On Tue, Jan 17, 2006 at 09:16:51PM +0100, Jan Engelhardt wrote:
> Hi,
>
> I could not find a clue on the first try on why xfs needs exportfs.
> The Kconfig says "select EXPORTFS if CONFIG_NFSD!=n", but there are no
> occurrences of CONFIG_NFS* or CONFIG_EXP* in any of the files in fs/xfs/.
> Did I miss something or this a superfluous line in Kconfig? Interestingly
> tho, `modinfo xfs.ko` returns "exportfs", so I suppose it's somewhere, well
> hidden. If so, where?
xfs_export.c, find_exported_dentry.
cheers.
--
Nathan
next prev parent reply other threads:[~2006-01-17 20:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-17 20:16 xfs depends on exportfs Jan Engelhardt
2006-01-17 20:42 ` Nathan Scott [this message]
2006-01-18 5:39 ` Keith Owens
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=20060118074223.A8500612@wobbly.melbourne.sgi.com \
--to=nathans@sgi.com \
--cc=jengelh@linux01.gwdg.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-xfs@oss.sgi.com \
/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;
as well as URLs for NNTP newsgroup(s).