Re: [PATCH v3] mm/hugetlb: add mempolicy check in the reservation routine

2020-07-27 Thread Mike Kravetz
On 7/27/20 5:19 PM, Andrew Morton wrote: > On Sat, 25 Jul 2020 16:07:49 +0800 Muchun Song > wrote: > >> In the reservation routine, we only check whether the cpuset meets >> the memory allocation requirements. But we ignore the mempolicy of >> MPOL_BIND case. If someone mmap hugetlb succeeds,

Re: [External] Re: [PATCH v3] mm/hugetlb: add mempolicy check in the reservation routine

2020-07-27 Thread Muchun Song
On Tue, Jul 28, 2020 at 8:19 AM Andrew Morton wrote: > > On Sat, 25 Jul 2020 16:07:49 +0800 Muchun Song > wrote: > > > In the reservation routine, we only check whether the cpuset meets > > the memory allocation requirements. But we ignore the mempolicy of > > MPOL_BIND case. If someone mmap

Re: [PATCH v3] mm/hugetlb: add mempolicy check in the reservation routine

2020-07-27 Thread Andrew Morton
On Sat, 25 Jul 2020 16:07:49 +0800 Muchun Song wrote: > In the reservation routine, we only check whether the cpuset meets > the memory allocation requirements. But we ignore the mempolicy of > MPOL_BIND case. If someone mmap hugetlb succeeds, but the subsequent > memory allocation may fail due

Re: [PATCH v3] mm/hugetlb: add mempolicy check in the reservation routine

2020-07-27 Thread Mike Kravetz
On 7/25/20 1:07 AM, Muchun Song wrote: > In the reservation routine, we only check whether the cpuset meets > the memory allocation requirements. But we ignore the mempolicy of > MPOL_BIND case. If someone mmap hugetlb succeeds, but the subsequent > memory allocation may fail due to mempolicy

[PATCH v3] mm/hugetlb: add mempolicy check in the reservation routine

2020-07-25 Thread Muchun Song
In the reservation routine, we only check whether the cpuset meets the memory allocation requirements. But we ignore the mempolicy of MPOL_BIND case. If someone mmap hugetlb succeeds, but the subsequent memory allocation may fail due to mempolicy restrictions and receives the SIGBUS signal. This