linux-kernel - Re: linux-next: Tree for January 23 (kvm)

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: <A6E711C3-9127-4B57-9BD2-0C00D773C8EA@suse.de>
Date:	Wed, 28 Jan 2009 11:20:16 +0100
From:	Alexander Graf <agraf@...e.de>
To:	Andrew Morton <akpm@...ux-foundation.org>
Cc:	Randy Dunlap <randy.dunlap@...cle.com>,
	Stephen Rothwell <sfr@...b.auug.org.au>,
	linux-next@...r.kernel.org, LKML <linux-kernel@...r.kernel.org>,
	avi@...hat.com, Marcelo Tosatti <mtosatti@...hat.com>
Subject: Re: linux-next: Tree for January 23 (kvm)


On 28.01.2009, at 10:51, Andrew Morton wrote:

> On Fri, 23 Jan 2009 12:34:24 -0800 Randy Dunlap <randy.dunlap@...cle.com 
> > wrote:
>
>> Stephen Rothwell wrote:
>>> Hi all,
>>>
>>> News:  I will be on leave next week, so there will probably be no
>>> linux-next release until Feb 2.
>>>
>>> Changes since 20090122:
>>
>>
>> kvm changes cause this build error on i386:
>>
>> when kvm is built as module:
>> ERROR: "__moddi3" [arch/x86/kvm/kvm.ko] undefined!
>>
>> or when kvm is built into the kernel image:
>> lapic.c:(.text+0x19276): undefined reference to `__moddi3'
>>
>>
>> I guess it's this line:
>> 	ns = ktime_to_ns(remaining) % apic->timer.period;
>>
>
> dammit, I just spent N minutes hunting down the same thing in
> the Jan 26 linux-next :(
>

Yeah, Clemens Foss posted a real fix on kvm@...r already.

Sorry for the fuss :-).

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