Re: [PATCH] mm/page_alloc: Wait for oom_lock before retrying.
From: Michal Hocko <mhocko@suse.com>
Date: 2016-12-14 12:44:39
On Wed 14-12-16 13:36:44, Petr Mladek wrote: [...]
There are basically two solution for this situation: 1. Fix printk() so that it does not block forever. This will get solved by the async printk patchset[*]. In the meantime, a particular sensitive location might be worked around by using printk_deferred() instead of printk()[**]
Absolutely!
2. Reduce the amount of messages. It is insane to report the same problem many times so that the same messages fill the entire log buffer. Note that the allocator is not the only sinner here.
sure and the ratelimit patch should help in that direction. show_mem for each allocation stall is really way too much. -- Michal Hocko SUSE Labs -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@kvack.org. For more info on Linux MM, see: http://www.linux-mm.org/ . Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>