public inbox for linux-next@vger.kernel.org
 help / color / mirror / Atom feed
From: Dave Chinner <david@fromorbit.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Pekka Enberg <penberg@cs.helsinki.fi>,
	Christoph Lameter <cl@linux-foundation.org>,
	linux-next@vger.kernel.org, Rik van Riel <riel@redhat.com>,
	Lachlan McIlroy <lachlan@sgi.com>,
	Christoph Hellwig <hch@infradead.org>
Subject: Re: linux-next: slab tree build failure
Date: Mon, 3 Nov 2008 16:14:33 +1100	[thread overview]
Message-ID: <20081103051433.GS19509@disturbed> (raw)
In-Reply-To: <20081103154221.e68a50f0.sfr@canb.auug.org.au>

On Mon, Nov 03, 2008 at 03:42:21PM +1100, Stephen Rothwell wrote:
> Hi all,
> 
> Today's linux-next build (powerpc ppc64_defconfig) failed like this:
> 
> fs/xfs/linux-2.6/xfs_super.c: In function 'xfs_init_zones':
> fs/xfs/linux-2.6/xfs_super.c:1714: error: 'xfs_vnode_zone' undeclared (first use in this function)
> 
> It is a mismerge (in the linux-next tree) between commits
> 7836dda725873a5ce05d216295a452f16ccaab72 ("[XFS] Combine the XFS and
> Linux inodes") form the xfs tree and
> 200d770048651d9a03266dc1bf031bb6f9e1363a ("Filesystem: XFS slab
> defragmentation") from the slab tree.

I didn't even know that the slab defrag stuff was being carried in
a tree anywhere. The xfs_vnode_zone has gone away, so I guess that
hunk can be dropped. defrag should really now target the xfs_inode_zone,
but it's going to need custom get and kick methods because it's
far different to the generic inode code now....

> I guess the latter patch needs to be dropped since its target is going
> away.
> 
> I fixed up the merge (see below) and can carry the fix for a few days.

Yeah, that will work for the moment. It's probably best that we
don't try to add defrag back into the XFS inode code until we've
sorted all the niggling problems as a result of the "combine..."
patch.

Cheers,

Dave.
-- 
Dave Chinner
david@fromorbit.com

  reply	other threads:[~2008-11-03  5:14 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-03  4:42 linux-next: slab tree build failure Stephen Rothwell
2008-11-03  5:14 ` Dave Chinner [this message]
2008-11-03  9:38   ` Pekka Enberg
  -- strict thread matches above, loose matches on Subject: below --
2009-06-19  4:16 Stephen Rothwell
2009-06-19 10:40 ` Benjamin Herrenschmidt
2009-06-22  9:09   ` Pekka Enberg
2009-09-07  5:37 Stephen Rothwell
2009-09-07  6:10 ` Pekka Enberg
2009-09-07  7:31   ` Stephen Rothwell
2009-09-07  7:43     ` Pekka Enberg
2009-09-07  8:29       ` Stephen Rothwell
2009-09-07  9:04       ` Heiko Carstens
2009-09-07  9:22         ` Pekka Enberg
2009-09-07  8:35   ` Catalin Marinas
2009-09-08 16:32     ` Luis R. Rodriguez
2009-12-07  4:11 Stephen Rothwell
2009-12-08  3:44 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=20081103051433.GS19509@disturbed \
    --to=david@fromorbit.com \
    --cc=cl@linux-foundation.org \
    --cc=hch@infradead.org \
    --cc=lachlan@sgi.com \
    --cc=linux-next@vger.kernel.org \
    --cc=penberg@cs.helsinki.fi \
    --cc=riel@redhat.com \
    --cc=sfr@canb.auug.org.au \
    /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