linux-kernel - Re: [tip:core/rcu] rcu: Add second diagnostic check for a possible CPU-hotplug race

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

Message-ID: <20090809110019.GA20236@elte.hu>
Date:	Sun, 9 Aug 2009 13:00:19 +0200
From:	Ingo Molnar <mingo@...e.hu>
To:	mingo@...hat.com, hpa@...or.com, paulmck@...ux.vnet.ibm.com,
	linux-kernel@...r.kernel.org, tglx@...utronix.de
Cc:	linux-tip-commits@...r.kernel.org
Subject: Re: [tip:core/rcu] rcu: Add second diagnostic check for a possible
	CPU-hotplug race


* tip-bot for Paul E. McKenney <paulmck@...ux.vnet.ibm.com> wrote:

> Commit-ID:  86f044729ee3e4d8885c17371ce5a76f6f321dc7
> Gitweb:     http://git.kernel.org/tip/86f044729ee3e4d8885c17371ce5a76f6f321dc7
> Author:     Paul E. McKenney <paulmck@...ux.vnet.ibm.com>
> AuthorDate: Wed, 5 Aug 2009 18:26:45 -0700
> Committer:  Ingo Molnar <mingo@...e.hu>
> CommitDate: Sun, 9 Aug 2009 12:42:48 +0200
> 
> rcu: Add second diagnostic check for a possible CPU-hotplug race

has a build problem too:

 kernel/built-in.o: In function `rcu_cpu_notified':
 (.text+0x1d787): undefined reference to `cpu_notified'
 kernel/built-in.o: In function `rcu_init':
 (.init.text+0x1174): undefined reference to `cpu_notified'
 kernel/built-in.o: In function `rcu_init':
 (.init.text+0x11a8): undefined reference to `cpu_notified'

Maybe we should simplify all those Kconfig rules? It's a maze.

	Ingo
--
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/