On 03/07/2018 05:00 PM, Oleg Babin wrote:
> After sysctl parameter 'vm.warn_high_order' is modified it can't be
> returned back to the default value MAX_ORDER+1, only to the fixed
> value 10.
> Set the maximum value to 100 which is always larger than any maximum
> order. Also set the default value to MAX_ORDER as it is already the
> value which can never be allocated.
> Also there is a logic to stop generating the warning after 32 occurences,
> but the logic is broken (the warning is generated even after the counter
> becomes less than zero). Modify the procedure of checking the counter.
> Signed-off-by: Oleg Babin <oba...@virtuozzo.com>
Acked-by: Andrey Ryabinin <aryabi...@virtuozzo.com>
Devel mailing list