Re: [PATCH] hugetlbfs: always use address space in inode for resv_map pointer

2019-05-09 Thread Mike Kravetz
On 5/9/19 4:11 PM, Andrew Morton wrote: > On Wed, 8 May 2019 13:16:09 -0700 Mike Kravetz > wrote: > >>> I think it is better to add fixes label, like: >>> Fixes: 58b6e5e8f1ad ("hugetlbfs: fix memory leak for resv_map") >>> >>> Since the commit 58b6e5e8f1a has been merged to stable, this patch al

Re: [PATCH] hugetlbfs: always use address space in inode for resv_map pointer

2019-05-09 Thread Andrew Morton
On Wed, 8 May 2019 13:16:09 -0700 Mike Kravetz wrote: > > I think it is better to add fixes label, like: > > Fixes: 58b6e5e8f1ad ("hugetlbfs: fix memory leak for resv_map") > > > > Since the commit 58b6e5e8f1a has been merged to stable, this patch also be > > needed. > > https://www.spinics.net

Re: [PATCH] hugetlbfs: always use address space in inode for resv_map pointer

2019-05-08 Thread Mike Kravetz
On 5/8/19 12:10 AM, yuyufen wrote: > On 2019/4/20 4:44, Mike Kravetz wrote: >> Continuing discussion about commit 58b6e5e8f1ad ("hugetlbfs: fix memory >> leak for resv_map") brought up the issue that inode->i_mapping may not >> point to the address space embedded within the inode at inode eviction

Re: [PATCH] hugetlbfs: always use address space in inode for resv_map pointer

2019-05-08 Thread yuyufen
On 2019/4/20 4:44, Mike Kravetz wrote: Continuing discussion about commit 58b6e5e8f1ad ("hugetlbfs: fix memory leak for resv_map") brought up the issue that inode->i_mapping may not point to the address space embedded within the inode at inode eviction time. The hugetlbfs truncate routine han

[PATCH] hugetlbfs: always use address space in inode for resv_map pointer

2019-04-19 Thread Mike Kravetz
Continuing discussion about commit 58b6e5e8f1ad ("hugetlbfs: fix memory leak for resv_map") brought up the issue that inode->i_mapping may not point to the address space embedded within the inode at inode eviction time. The hugetlbfs truncate routine handles this by explicitly using inode->i_data.