linux-kernel - Re: linux-next: percpu/kvm/tip 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>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20091102100735.GB16963@elte.hu>
Date:	Mon, 2 Nov 2009 11:07:35 +0100
From:	Ingo Molnar <mingo@...e.hu>
To:	Avi Kivity <avi@...hat.com>
Cc:	Stephen Rothwell <sfr@...b.auug.org.au>, Tejun Heo <tj@...nel.org>,
	Rusty Russell <rusty@...tcorp.com.au>,
	Christoph Lameter <cl@...ux-foundation.org>,
	linux-next@...r.kernel.org, linux-kernel@...r.kernel.org,
	Thomas Gleixner <tglx@...utronix.de>,
	"H. Peter Anvin" <hpa@...or.com>,
	Peter Zijlstra <peterz@...radead.org>
Subject: Re: linux-next: percpu/kvm/tip tree build failure


* Avi Kivity <avi@...hat.com> wrote:

> On 11/02/2009 07:17 AM, Stephen Rothwell wrote:
>> Hi all,
>>
>> Today's linux-next build (x86_64 allmodconfig) failed like this:
>>
>> kernel/user-return-notifier.c: In function 'fire_user_return_notifiers':
>> kernel/user-return-notifier.c:45: error: expected expression before ')' token
>>
>> Introduced by commit 7c68af6e32c73992bad24107311f3433c89016e2 ("core,
>> x86: Add user return notifiers") from the tip and kvm trees but revealed
>> by commit e0fdb0e050eae331046385643618f12452aa7e73 ("percpu: add __percpu
>> for sparse") from the percpu tree.  Before that percpu tree commit,
>> "put_cpu_var()" would compile without error (even though it really needs
>> a parameter).
>>
>> I have applied the following patch for today.
>>    
>
> Ingo, can you queue this on x86/entry?

Already done, tested and pushed out.

	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/