linux-kernel - locking/pvqspinlock, x86: undefined CONFIG_QUEUED

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]

Message-ID: <CAD3Xx4KZUmZCADtrw6bUxdxxgXwFyDoURr6eWu0M4AnrKG+Xsg@mail.gmail.com>
Date:	Mon, 11 May 2015 09:42:51 +0200
From:	Valentin Rothberg <valentinrothberg@...il.com>
To:	peterz@...radead.org
Cc:	tglx@...utronix.de, mingo@...hat.com, hpa@...or.com,
	linux-kernel@...r.kernel.org,
	virtualization@...ts.linux-foundation.org,
	Paul Bolle <pebolle@...cali.nl>,
	Andreas Ruprecht <andreas.ruprecht@....de>,
	hengelein Stefan <stefan.hengelein@....de>
Subject: locking/pvqspinlock, x86: undefined CONFIG_QUEUED_SPINLOCKS

Hi Peter,

your commit f233f7f1581e ("locking/pvqspinlock, x86: Implement the
paravirt qspinlock call patching") is in today's linux-next tree
(i.e., next-20150511).  The two #ifdef blocks listed below cannot be
compiled at the current state since CONFIG_QUEUED_SPINLOCKS does not
exist:

+#if defined(CONFIG_PARAVIRT_SPINLOCKS) && defined(CONFIG_QUEUED_SPINLOCKS)
[...]
+#if defined(CONFIG_PARAVIRT_SPINLOCKS) && defined(CONFIG_QUEUED_SPINLOCKS)

It seems that it's just a typo, since QUEUED_SPINLOCK (i.e., without
last S) is defined in kernel/Kconfig.locks.

I detected this issue with scripts/checkkconfigsymbols.py by diffing
today's and the previous next tree.

Kind regards,
 Valentin
--
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/