Comment 15 for bug 1528101

Revision history for this message
bugproxy (bugproxy) wrote : Comment bridged from LTC Bugzilla

------- Comment From <email address hidden> 2016-03-28 16:01 EDT-------
Minor changes to the kernel handling of user_min_free_kbytes appears to be the ideal solution here since it would have benefits outside of the kdump environment. Currently, it appears that it is too easy to manually set a completely inappropriate value. Elsewhere, the value is capped at either 65536 or 5% of lowmem, but it appears that the user provided value is not run through the same sanity checks (see init_per_zone_wmark_min() as an example).