linux-kernel - Re: [broken-out-2007-07-20-00-22] XFS build error

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-Id: <20070720093525.3c709be3.akpm@linux-foundation.org>
Date:	Fri, 20 Jul 2007 09:35:25 -0700
From:	Andrew Morton <akpm@...ux-foundation.org>
To:	"Michal Piotrowski" <michal.k.k.piotrowski@...il.com>
Cc:	"David Chinner" <dgc@....com>, xfs-masters@....sgi.com,
	LKML <linux-kernel@...r.kernel.org>
Subject: Re: [broken-out-2007-07-20-00-22] XFS build error

On Fri, 20 Jul 2007 17:02:13 +0200 "Michal Piotrowski" <michal.k.k.piotrowski@...il.com> wrote:

> Hi David,
> 
> I get this build error on the latest -mm snapshot
> 
> fs/xfs/linux-2.6/xfs_file.c:483: error: unknown field 'populate'
> specified in initializer
> fs/xfs/linux-2.6/xfs_file.c:483: error: 'filemap_populate' undeclared
> here (not in a function)
> fs/xfs/linux-2.6/xfs_file.c:483: warning: excess elements in struct initializer
> fs/xfs/linux-2.6/xfs_file.c:483: warning: (near initialization for
> 'xfs_file_vm_ops')
> make[2]: *** [fs/xfs/linux-2.6/xfs_file.o] Error 1
> make[1]: *** [fs/xfs] Error 2
> make: *** [fs] Error 2
> 
> quilt patches fs/xfs/linux-2.6/xfs_file.c
> patches/git-xfs.patch
> patches/git-xfs-fixup.patch

That was my lame, untested attempt to fix git conflicts in the xfs tree.

That -mm snapshot was a secret upload for Nick - you weren't supposed to
notice it ;)

I'd be stunned if it booted.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/