public inbox for linux-next@vger.kernel.org 
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb•auug.org.au>
To: David Chinner <david@fromorbit•com>, xfs-masters@oss•sgi.com
Cc: linux-next@vger•kernel.org, Lachlan McIlroy <lachlan@sgi•com>,
	linux-fsdevel@vger•kernel.org
Subject: linux-next: xfs tree build failure
Date: Thu, 30 Oct 2008 13:23:24 +1100	[thread overview]
Message-ID: <20081030132324.0d619fdd.sfr@canb.auug.org.au> (raw)

Hi David,

Today's linux-next build (powerpc ppc64_defconfig) failed like this:

ERROR: "inode_wait" [fs/xfs/xfs.ko] undefined!

Caused by commit 676a7711ee281c3bf41db18e29e296584de82793 ("[XFS] Fix
race when looking up reclaimable inodes") which introduced a use of
wait_on_inode() which is an inline that calls inode_wait().

I applied the following patch (probably wrong :-)).
-- 
Cheers,
Stephen Rothwell                    sfr@canb•auug.org.au
http://www.canb.auug.org.au/~sfr/

From: Stephen Rothwell <sfr@canb•auug.org.au>
Date: Thu, 30 Oct 2008 13:19:46 +1100
Subject: [PATCH] fs: xfs needs inode_wait to be exported

Since wait_on_inode() references it.

Signed-off-by: Stephen Rothwell <sfr@canb•auug.org.au>
---
 fs/inode.c |    1 +
 1 files changed, 1 insertions(+), 0 deletions(-)

diff --git a/fs/inode.c b/fs/inode.c
index f84ba33..098a244 100644
--- a/fs/inode.c
+++ b/fs/inode.c
@@ -1334,6 +1334,7 @@ int inode_wait(void *word)
 	schedule();
 	return 0;
 }
+EXPORT_SYMBOL(inode_wait);
 
 /*
  * If we try to find an inode in the inode hash while it is being
-- 
1.5.6.5

             reply	other threads:[~2008-10-30  2:23 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-30  2:23 Stephen Rothwell [this message]
2008-10-30  9:08 ` linux-next: xfs tree build failure Dave Chinner
2008-11-05  2:20   ` Stephen Rothwell
2008-11-05 20:47     ` Dave Chinner
2008-11-06 15:27       ` Christoph Hellwig
2008-11-07  5:06         ` Stephen Rothwell
2008-11-11  2:05           ` Lachlan McIlroy
2008-11-11  2:11             ` Stephen Rothwell
  -- strict thread matches above, loose matches on Subject: below --
2008-12-03 23:16 Stephen Rothwell
2008-12-04  5:20 ` Eric Sandeen
2009-03-10  2:45 Stephen Rothwell
2009-03-11 22:52 ` Dave Chinner
2009-03-12  1:04 ` Stephen Rothwell
2009-03-15 12:18   ` Dave Chinner
2009-07-03  0:05 Stephen Rothwell
2009-09-02  1:25 Stephen Rothwell
2009-09-02  1:28 ` Christoph Hellwig
2009-09-02  1:54   ` Felix Blyakher
2009-09-02  2:00     ` Stephen Rothwell

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=20081030132324.0d619fdd.sfr@canb.auug.org.au \
    --to=sfr@canb$(echo .)auug.org.au \
    --cc=david@fromorbit$(echo .)com \
    --cc=lachlan@sgi$(echo .)com \
    --cc=linux-fsdevel@vger$(echo .)kernel.org \
    --cc=linux-next@vger$(echo .)kernel.org \
    --cc=xfs-masters@oss$(echo .)sgi.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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