linux-kernel - Re: mmotm 2013-01-11-15-47 (trouble starting 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]

Date:	Sat, 12 Jan 2013 16:47:32 +0100
From:	Zlatko Calusic <zlatko.calusic@...on.hr>
To:	akpm@...ux-foundation.org
CC:	mm-commits@...r.kernel.org, linux-kernel@...r.kernel.org,
	linux-mm@...ck.org, linux-fsdevel@...r.kernel.org,
	linux-next@...r.kernel.org
Subject: Re: mmotm 2013-01-11-15-47 (trouble starting kvm)

On 12.01.2013 00:48, akpm@...ux-foundation.org wrote:
> A git tree which contains the memory management portion of this tree is
> maintained at git://git.kernel.org/pub/scm/linux/kernel/git/mhocko/mm.git
> by Michal Hocko.  It contains the patches which are between the

The last commit I see in this tree is:

commit a0d271cbfed1dd50278c6b06bead3d00ba0a88f9
Author: Linus Torvalds <torvalds@...ux-foundation.org>
Date:   Sun Sep 30 16:47:46 2012 -0700

     Linux 3.6

Is it dead? Or am I doing something wrong?

> A full copy of the full kernel tree with the linux-next and mmotm patches
> already applied is available through git within an hour of the mmotm
> release.  Individual mmotm releases are tagged.  The master branch always
> points to the latest release, so it's constantly rebasing.
>
> http://git.cmpxchg.org/?p=linux-mmotm.git;a=summary
>
> This mmotm tree contains the following patches against 3.8-rc3:
> (patches marked "*" will be included in linux-next)
>
> * lockdep-rwsem-provide-down_write_nest_lock.patch
> * mm-mmap-annotate-vm_lock_anon_vma-locking-properly-for-lockdep.patch

Had to revert the above two patches to start KVM (win7) successfully. 
Otherwise it would livelock on some semaphore, it seems. Couldn't kill 
it, ps output would stuck, even reboot didn't work (had to use SysRQ).

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