| 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, 29 Jun 2011 13:11:00 -0700 From: Andi Kleen <andi@...stfloor.org> To: Dave Hansen <dave@...ux.vnet.ibm.com> Cc: Ankita Garg <ankita@...ibm.com>, linux-arm-kernel@...ts.infradead.org, linux-mm@...ck.org, linux-kernel@...r.kernel.org, linux-pm@...ts.linux-foundation.org, svaidy@...ux.vnet.ibm.com, thomas.abraham@...aro.org, "Paul E. McKenney" <paulmck@...ux.vnet.ibm.com>, KAMEZAWA Hiroyuki <kamezawa.hiroyu@...fujitsu.com>, Matthew Garrett <mjg59@...f.ucam.org>, Arjan van de Ven <arjan@...radead.org> Subject: Re: [PATCH 00/10] mm: Linux VM Infrastructure to support Memory Power Management Dave Hansen <dave@...ux.vnet.ibm.com> writes: > > It's also going to be a pain to track kernel references. On x86, our Even if you tracked them what would you do with them? It's quite hard to stop using arbitary kernel memory (see all the dancing memory-failure does) You need to track the direct accesses to user data which happens to be accessed through the direct mapping. Also it will be always unreliable because this all won't track DMA. For that you would also need to track in the dma_* infrastructure, which will likely get seriously expensive. -Andi -- ak@...ux.intel.com -- Speaking for myself only -- 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