| 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: Tue, 12 Oct 2010 15:14:14 +0200 From: Andi Kleen <andi@...stfloor.org> To: KOSAKI Motohiro <kosaki.motohiro@...fujitsu.com> Cc: Andi Kleen <andi@...stfloor.org>, linux-mm@...ck.org, linux-kernel@...r.kernel.org, fengguang.wu@...el.com, akpm@...ux-foundation.org Subject: Re: RFC: Implement hwpoison on free for soft offlining > To me, it's no problem if this keep 64bit only. IOW, I only dislike to > add 32bit page flags. > > Yeah, memory corruption is very crap and i think your effort has a lot > of worth :) Thanks. > > > offtopic, I don't think CONFIG_MEMORY_FAILURE and CONFIG_HWPOISON_ON_FREE > are symmetric nor easy understandable. can you please consider naming change? > (example, CONFIG_HWPOISON/CONFIG_HWPOISON_ON_FREE, > CONFIG_MEMORY_FAILURE/CONFIG_MEMORY_FAILURE_SOFT_OFFLINE) memory-failure was the old name before hwpoison as a term was invented by Andrew. In theory it would make sense to rename everything to "hwpoison" now. But I decided so far the disadvantages from breaking user configurations and the impact from renaming files far outweight the small benefits in clarity. So right now I prefer to keep the status quo, but name everything new hwpoison. -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