__GFP_NOFAIL is also very badly named: patently it can and does fail,
when PF_MEMALLOC or PF_MEMDIE or not __GFP_WAIT. Or is the idea that
its users might as well oops when it does fail? Should its users be
changed to use the less perniciously named __GFP_REPEAT, or should
__alloc_pages be changed to deadlock more thoroughly?
Hugh
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/