| 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: Thu, 17 Mar 2011 16:21:50 +0100 From: Andi Kleen <andi@...stfloor.org> To: Hidetoshi Seto <seto.hidetoshi@...fujitsu.com> Cc: Andi Kleen <andi@...stfloor.org>, Andrea Arcangeli <aarcange@...hat.com>, Andrew Morton <akpm@...ux-foundation.org>, Huang Ying <ying.huang@...el.com>, Jin Dongming <jin.dongming@...css.fujitsu.com>, linux-kernel@...r.kernel.org Subject: Re: [PATCH 3/4] Check whether pages are poisoned before copying > At least copy to the last page of the huge page is performed after > all preceding copies are finished. So I'm not sure it is really > "a few" or not. > Still I think making the window smaller than now is worthwhile, > no matter it is change from 0.1% to 0.01%, or from 0.01% to 0.001%. Note that hwpoison will never reach 100% coverage. That's impossible. But to get nearer to 100% it's better to concentrate of the paths that affect long time windows and significant amounts of memory. What those are is often non-obvious and needs measurements. > > Or did you find the downside of the check here? The usual problem is how to test it. That tends to be harder than just writing the code. If it's not tested it's probably not worth having. -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