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
| ||
|
Date: Wed, 16 Apr 2008 14:02:13 -0500 From: Robin Holt <holt@....com> To: Christoph Lameter <clameter@....com> Cc: Robin Holt <holt@....com>, Andrea Arcangeli <andrea@...ranet.com>, akpm@...ux-foundation.org, Nick Piggin <npiggin@...e.de>, Steve Wise <swise@...ngridcomputing.com>, Peter Zijlstra <a.p.zijlstra@...llo.nl>, linux-mm@...ck.org, Kanoj Sarcar <kanojsarcar@...oo.com>, Roland Dreier <rdreier@...co.com>, Jack Steiner <steiner@....com>, linux-kernel@...r.kernel.org, Avi Kivity <avi@...ranet.com>, kvm-devel@...ts.sourceforge.net, general@...ts.openfabrics.org, Hugh Dickins <hugh@...itas.com> Subject: Re: [PATCH 1 of 9] Lock the entire mm to prevent any mmu related operation to happen On Wed, Apr 16, 2008 at 11:35:38AM -0700, Christoph Lameter wrote: > On Wed, 16 Apr 2008, Robin Holt wrote: > > > I don't think this lock mechanism is completely working. I have > > gotten a few failures trying to dereference 0x100100 which appears to > > be LIST_POISON1. > > How does xpmem unregistering of notifiers work? For the tests I have been running, we are waiting for the release callout as part of exit. Thanks, Robin -- 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