public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: Andrew Morton <akpm@osdl.org>
Cc: Paul Blazejowski <diffie@gmail.com>,
	linux-kernel@vger.kernel.org, Nathan Scott <nathans@sgi.com>
Subject: Re: 2.6.11-rc2-mm2
Date: Mon, 31 Jan 2005 14:51:00 +0000	[thread overview]
Message-ID: <20050131145100.GA13161@infradead.org> (raw)
In-Reply-To: <20050129235653.1d9ba5a9.akpm@osdl.org>

On Sat, Jan 29, 2005 at 11:56:53PM -0800, Andrew Morton wrote:
> Paul Blazejowski <diffie@gmail.com> wrote:
> >
> > Kernel compile errors here, i think this might be XFS related...
> > 
> >  fs/built-in.o(.text+0x52a93): In function `linvfs_decode_fh':
> >  : undefined reference to `find_exported_dentry'
> >  make: *** [.tmp_vmlinux1] Error 1
> 
> bix:/home/akpm> grep EXPORT x
> CONFIG_XFS_EXPORT=y
> CONFIG_EXPORTFS=m
> 
> That isn't going to work.  Something like this, perhaps?


This patch (implementing Roman's suggestion) should fix it:

--- linux-2.6.11-rc2-mm1/fs/xfs/Kconfig~	2005-01-31 15:56:45.969973712 +0100
+++ linux-2.6.11-rc2-mm1/fs/xfs/Kconfig	2005-01-31 15:57:12.236974472 +0100
@@ -3,6 +3,7 @@
 config XFS_FS
 	tristate "XFS filesystem support"
 	select QSORT
+	select EXPORTFS if NFSD
 	help
 	  XFS is a high performance journaling filesystem which originated
 	  on the SGI IRIX platform.  It is completely multi-threaded, can

  parent reply	other threads:[~2005-01-31 14:51 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-30  7:34 2.6.11-rc2-mm2 Paul Blazejowski
2005-01-30  7:56 ` 2.6.11-rc2-mm2 Andrew Morton
2005-01-30 10:54   ` 2.6.11-rc2-mm2 Christoph Hellwig
2005-01-30 10:57     ` 2.6.11-rc2-mm2 Christoph Hellwig
2005-01-30 12:00       ` 2.6.11-rc2-mm2 Adrian Bunk
2005-01-30 12:12         ` 2.6.11-rc2-mm2 Adrian Bunk
2005-01-30 20:35           ` 2.6.11-rc2-mm2 Paul Blazejowski
2005-01-30 23:00           ` 2.6.11-rc2-mm2 Roman Zippel
2005-01-30 23:10             ` 2.6.11-rc2-mm2 Adrian Bunk
2005-01-30 23:36               ` 2.6.11-rc2-mm2 Roman Zippel
2005-01-31  7:31                 ` 2.6.11-rc2-mm2 Christoph Hellwig
2005-01-31 15:10                 ` 2.6.11-rc2-mm2 Adrian Bunk
2005-01-31 15:16                   ` 2.6.11-rc2-mm2 Roman Zippel
2005-01-31 19:42                     ` 2.6.11-rc2-mm2 Adrian Bunk
2005-01-30 11:38   ` 2.6.11-rc2-mm2 Adrian Bunk
2005-01-31 14:51   ` Christoph Hellwig [this message]
2005-01-30 20:45 ` 2.6.11-rc2-mm2 Paul Blazejowski
2005-01-31 19:37   ` 2.6.11-rc2-mm2 Chuck Harding
  -- strict thread matches above, loose matches on Subject: below --
2005-01-29 21:11 2.6.11-rc2-mm2 Andrew Morton
2005-01-29 22:52 ` 2.6.11-rc2-mm2 Brice Goglin
2005-01-29 23:10 ` 2.6.11-rc2-mm2 Sean Neakums
2005-01-29 23:56   ` 2.6.11-rc2-mm2 Sean Neakums
2005-01-30  6:20 ` 2.6.11-rc2-mm2 Andrew Nelson
2005-01-30 11:03   ` 2.6.11-rc2-mm2 Rafael J. Wysocki
2005-01-31 21:15 ` 2.6.11-rc2-mm2 Andre Eisenbach
2005-01-31 21:46   ` 2.6.11-rc2-mm2 Laurent Riffard
2005-02-01  1:26     ` 2.6.11-rc2-mm2 Jim Nelson
2005-02-01 17:25     ` 2.6.11-rc2-mm2 Andre Eisenbach
2005-02-01  9:17 ` 2.6.11-rc2-mm2 Nick Piggin

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=20050131145100.GA13161@infradead.org \
    --to=hch@infradead.org \
    --cc=akpm@osdl.org \
    --cc=diffie@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nathans@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