> 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@xxxxxxxxxxxxxxx -- Speaking for myself only. -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@xxxxxxxxxx For more info on Linux MM, see: http://www.linux-mm.org/ . Don't email: <a href=mailto:"dont@xxxxxxxxx";> email@xxxxxxxxx </a>