Re: [PATCH] mm: respect arch_dup_mmap() return value

2018-08-23 Thread Michal Hocko
On Wed 22-08-18 22:12:29, Nadav Amit wrote: > Commit d70f2a14b72a4 ("include/linux/sched/mm.h: uninline > mmdrop_async(), etc") ignored the return value of arch_dup_mmap(). As a > result, on x86, a failure to duplicate the LDT (e.g., due to memory > allocation error), would leave the duplicated

Re: [PATCH] mm: respect arch_dup_mmap() return value

2018-08-23 Thread Michal Hocko
On Wed 22-08-18 22:12:29, Nadav Amit wrote: > Commit d70f2a14b72a4 ("include/linux/sched/mm.h: uninline > mmdrop_async(), etc") ignored the return value of arch_dup_mmap(). As a > result, on x86, a failure to duplicate the LDT (e.g., due to memory > allocation error), would leave the duplicated

[PATCH] mm: respect arch_dup_mmap() return value

2018-08-22 Thread Nadav Amit
Commit d70f2a14b72a4 ("include/linux/sched/mm.h: uninline mmdrop_async(), etc") ignored the return value of arch_dup_mmap(). As a result, on x86, a failure to duplicate the LDT (e.g., due to memory allocation error), would leave the duplicated memory mapping in an inconsistent state. Fix by

[PATCH] mm: respect arch_dup_mmap() return value

2018-08-22 Thread Nadav Amit
Commit d70f2a14b72a4 ("include/linux/sched/mm.h: uninline mmdrop_async(), etc") ignored the return value of arch_dup_mmap(). As a result, on x86, a failure to duplicate the LDT (e.g., due to memory allocation error), would leave the duplicated memory mapping in an inconsistent state. Fix by