linux-kernel - linux-next: Linus' tree build failure

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>] [day] [month] [year] [list]

Date:	Mon, 9 Feb 2009 19:29:58 +1100
From:	Stephen Rothwell <sfr@...b.auug.org.au>
To:	Chris Mason <chris.mason@...cle.com>
Cc:	linux-next@...r.kernel.org, LKML <linux-kernel@...r.kernel.org>,
	Linus <torvalds@...ux-foundation.org>
Subject: linux-next:  Linus' tree build failure

Hi Chris,

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

fs/btrfs/locking.c: In function 'btrfs_path_lock_waiting':
fs/btrfs/locking.c:254: error: implicit declaration of function '__raw_spin_is_contended'

CONFIG_PREEMPT is not set (since CONFIG_PREEMPT_NONE takes precedence
over it) which means that CONFIG_GENERIC_LOCKBREAK is not set (since it
depends on CONFIG_PREEMPT - at least on powerpc). So spin_is_contended()
is __raw_spin_is_contended().

__raw_spin_is_contended is only defined for UP, MIPS and X86.

Commit b4ce94de9b4d64e8ab3cf155d13653c666e22b9b ("Btrfs: Change btree
locking to use explicit blocking points") from Linus' tree added the
first generic non CONFIG_PREEMPT usage via a call to spin_is_contended().

I got past this for today by building the PowerPC allyesconfig without
btrfs.
-- 
Cheers,
Stephen Rothwell                    sfr@...b.auug.org.au
http://www.canb.auug.org.au/~sfr/

Content of type "application/pgp-signature" skipped