2013-04-29 01:29:50

by Stephen Rothwell

[permalink] [raw]
Subject: linux-next: build failure after merge of the xfs tree

Hi all,

After merging the xfs tree, today's linux-next build (powerpc
ppc64_defconfig) failed like this:

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

Probably caused by commit 3fe58f30b4fc ("xfs: add CRC checks for quota
blocks").

I have used the xfs tree from next-20130426 for today.
--
Cheers,
Stephen Rothwell [email protected]
http://www.canb.auug.org.au/~sfr/


Attachments:
(No filename) (402.00 B)
(No filename) (836.00 B)
Download all attachments

2013-04-29 01:40:08

by Dave Chinner

[permalink] [raw]
Subject: Re: linux-next: build failure after merge of the xfs tree

On Mon, Apr 29, 2013 at 11:29:43AM +1000, Stephen Rothwell wrote:
> Hi all,
>
> After merging the xfs tree, today's linux-next build (powerpc
> ppc64_defconfig) failed like this:
>
> ERROR: "xfs_dquot_buf_ops" [fs/xfs/xfs.ko] undefined!
>
> Probably caused by commit 3fe58f30b4fc ("xfs: add CRC checks for quota
> blocks").
>
> I have used the xfs tree from next-20130426 for today.

CONFIG_XFS_QUOTA=y will fix it.

Or, alternatively, apply this patch:

http://oss.sgi.com/pipermail/xfs/2013-April/025434.html

Cheers,

Dave.
--
Dave Chinner
[email protected]

2013-04-30 18:36:55

by Ben Myers

[permalink] [raw]
Subject: Re: linux-next: build failure after merge of the xfs tree

Hey Stephen and Dave,

On Mon, Apr 29, 2013 at 11:40:02AM +1000, Dave Chinner wrote:
> On Mon, Apr 29, 2013 at 11:29:43AM +1000, Stephen Rothwell wrote:
> > Hi all,
> >
> > After merging the xfs tree, today's linux-next build (powerpc
> > ppc64_defconfig) failed like this:
> >
> > ERROR: "xfs_dquot_buf_ops" [fs/xfs/xfs.ko] undefined!
> >
> > Probably caused by commit 3fe58f30b4fc ("xfs: add CRC checks for quota
> > blocks").
> >
> > I have used the xfs tree from next-20130426 for today.
>
> CONFIG_XFS_QUOTA=y will fix it.
>
> Or, alternatively, apply this patch:
>
> http://oss.sgi.com/pipermail/xfs/2013-April/025434.html

I applied this patch so it should be fixed today.

Regards,
Ben