On Wed, Dec 05, 2012 at 10:13:42PM +0000, Luck, Tony wrote: > > This patch fixes the warning from __list_del_entry() which is triggered > > when a process tries to do free_huge_page() for a hwpoisoned hugepage. > > Ultimately it would be nice to avoid poisoning huge pages. Generally we know the > location of the poison to a cache line granularity (but sometimes only to a 4K > granularity) ... and it is rather inefficient to take an entire 2M page out of service. > With 1G pages things would be even worse!! Thanks for the comment. And yes, it's remaining work to be done. > It also makes life harder for applications that would like to catch the SIGBUS > and try to take their own recovery actions. Losing more data than they really > need to will make it less likely that they can do something to work around the > loss. > > Has anyone looked at how hard it might be to have the code in memory-failure.c > break up a huge page and only poison the 4K that needs to be taken out of service? This work is one of my interest and became a bit easier than used to be, because now transparent hugepage works commonly and some of code can be copied from or shared with it. Thanks, Naoya -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@xxxxxxxxx. For more info on Linux MM, see: http://www.linux-mm.org/ . Don't email: <a href=mailto:"dont@xxxxxxxxx";> email@xxxxxxxxx </a>