linux-kernel - Re: [GIT PULL v2] sched: Make sleep inside atomic detection work on !PREEMPT

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: <20110701164425.GG8508@somewhere>
Date:	Fri, 1 Jul 2011 18:44:27 +0200
From:	Frederic Weisbecker <fweisbec@...il.com>
To:	Ingo Molnar <mingo@...e.hu>
Cc:	LKML <linux-kernel@...r.kernel.org>,
	"Paul E. McKenney" <paulmck@...ux.vnet.ibm.com>,
	Peter Zijlstra <a.p.zijlstra@...llo.nl>,
	Randy Dunlap <randy.dunlap@...cle.com>,
	Thomas Gleixner <tglx@...utronix.de>
Subject: Re: [GIT PULL v2] sched: Make sleep inside atomic detection work on
 !PREEMPT

On Fri, Jul 01, 2011 at 05:05:17PM +0200, Ingo Molnar wrote:
> 
> -tip testing also found that m32r fails to build:
> 
> /home/mingo/tip/kernel/sched.c: In function 'preempt_schedule':
> /home/mingo/tip/kernel/sched.c:4364: error: implicit declaration of function 'add_preempt_count_notrace'
> /home/mingo/tip/kernel/sched.c:4366: error: implicit declaration of function 'sub_preempt_count_notrace'
> 
> due to:
> 
> bdd4e85dc36cdbcfc1608a5b2a17c80a9db8986a is the first bad commit
> commit bdd4e85dc36cdbcfc1608a5b2a17c80a9db8986a
> Author: Frederic Weisbecker <fweisbec@...il.com>
> Date:   Wed Jun 8 01:13:27 2011 +0200
> 
>     sched: Isolate preempt counting in its own config option
> 
> Thanks,
> 
> 	Ingo

I have no clue how that did happen.

Can you send me your config?

Thanks.
--
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/