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: <20100126213853.GY30452@random.random>
Date:	Tue, 26 Jan 2010 22:38:53 +0100
From:	Andrea Arcangeli <aarcange@...hat.com>
To:	Robin Holt <holt@....com>
Cc:	Jack Steiner <steiner@....com>, cl@...ux-foundation.org,
	mingo@...e.hu, tglx@...utronix.de, linux-mm@...ck.org,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH] - Fix unmap_vma() bug related to mmu_notifiers

On Tue, Jan 26, 2010 at 03:29:04PM -0600, Robin Holt wrote:
> On Mon, Jan 25, 2010 at 10:16:15PM +0100, Andrea Arcangeli wrote:
> > The old patches are in my ftp area, they should still apply, you
> > should concentrate testing with those additional ones applied, then it
> > will work for xpmem too ;)
> 
> Andrea, could you point me at your ftp area?

Sure, this is the very latest version I maintained:

http://www.kernel.org/pub/linux/kernel/people/andrea/patches/v2.6/2.6.26-rc7/mmu-notifier-v18/

Note, it may be an option to make mmu notifier sleepable through
.config, unless people uses xpmem there is no reason to add
refcounting to vmas. That is something we'd pay even if no KVM is used
and no mmu notifer is used. I think the ideal is that anon-vma lock
should be a rwspinlock and only rcu (no refcounting) with
MMU_NOTIFIER_SLEEPABLE=n, and a read-write sem + refcounting if
MMU_NOTIFIER_SLEEPABLE=y. MMU_NOTIFIER_SLEEPABLE doesn't need to be
user visible, simply XPMEM=y will automatically set
MMU_NOTIFIER_SLEEPABLE=y.
--
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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ