xfs-masters
[Top] [All Lists]

[xfs-masters] Re: linux-next: xfs tree build failure

To: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
Subject: [xfs-masters] Re: linux-next: xfs tree build failure
From: Dave Chinner <david@xxxxxxxxxxxxx>
Date: Thu, 30 Oct 2008 20:08:32 +1100
Cc: xfs-masters@xxxxxxxxxxx, linux-next@xxxxxxxxxxxxxxx, Lachlan McIlroy <lachlan@xxxxxxx>, linux-fsdevel@xxxxxxxxxxxxxxx
In-reply-to: <20081030132324.0d619fdd.sfr@xxxxxxxxxxxxxxxx>
Mail-followup-to: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>, xfs-masters@xxxxxxxxxxx, linux-next@xxxxxxxxxxxxxxx, Lachlan McIlroy <lachlan@xxxxxxx>, linux-fsdevel@xxxxxxxxxxxxxxx
References: <20081030132324.0d619fdd.sfr@xxxxxxxxxxxxxxxx>
Reply-to: xfs-masters@xxxxxxxxxxx
Sender: xfs-masters-bounce@xxxxxxxxxxx
User-agent: Mutt/1.5.18 (2008-05-17)
On Thu, Oct 30, 2008 at 01:23:24PM +1100, Stephen Rothwell wrote:
> 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().

Putting a non-exported symbol in an inline function in a header file
that is full of exported functions.  That's pretty anti-social. ;)

> I applied the following patch (probably wrong :-)).

I think it's probably the only solution - we need to wait until
the I_LOCK bit is cleared from the inode and AFAICT wait_on_inode()
is the only way to do it.

Christoph?

Cheers,

Dave.
-- 
Dave Chinner
david@xxxxxxxxxxxxx


<Prev in Thread] Current Thread [Next in Thread>