All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eric Sandeen <sandeen@sandeen.net>
To: sekharan@us.ibm.com
Cc: XFS mailing list <xfs@oss.sgi.com>
Subject: Re: xfs module insert fails with "xfs: Unknown symbol exportfs_decode_fh (err 0)"
Date: Fri, 26 Apr 2013 13:02:37 -0500	[thread overview]
Message-ID: <517AC13D.9000802@sandeen.net> (raw)
In-Reply-To: <1366997050.4098.14.camel@chandra-dt.ibm.com>

On 4/26/13 12:24 PM, Chandra Seetharaman wrote:
> Hello,
> 
> When I tried to insert xfs module in my test machine it failed with 
> 
> 	xfs: Unknown symbol exportfs_decode_fh (err 0).

so don't use insmod, use modprobe :)

> Found out that I did not have CONFIG_EXPORTFS enabled in my kernel
> config. 

Oh, hum. But fs/xfs/Kconfig:

config XFS_FS
        tristate "XFS filesystem support"
        depends on BLOCK
        select EXPORTFS

it should be turned on automatically.  That seems to be the problem,
why wasn't it for your case?

> All .*by_handle code in XFS is open coded. Wondering if they should be
> under #ifdef CONFIG_EXPORTFS ?

CONFIG_EXPORTFS is supposed to be on if xfs is selected, unless something
changed recently.

-Eric

> I can create a patch, but wanted to find out if it is indeed needed :)
> 
> Regards,
> 
> Chandra
> 
> 
> 
> 
> _______________________________________________
> xfs mailing list
> xfs@oss.sgi.com
> http://oss.sgi.com/mailman/listinfo/xfs
> 

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

  reply	other threads:[~2013-04-26 18:02 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-26 17:24 xfs module insert fails with "xfs: Unknown symbol exportfs_decode_fh (err 0)" Chandra Seetharaman
2013-04-26 18:02 ` Eric Sandeen [this message]
2013-04-26 18:29   ` Chandra Seetharaman
2013-04-26 18:16 ` Ben Myers
2013-04-26 21:46   ` Dave Chinner

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=517AC13D.9000802@sandeen.net \
    --to=sandeen@sandeen.net \
    --cc=sekharan@us.ibm.com \
    --cc=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.