linux-kernel - Re: [PATCH 15/18] mm, hugetlb: move up anon_vma

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Mon, 29 Jul 2013 15:19:15 -0400
From:	Naoya Horiguchi <n-horiguchi@...jp.nec.com>
To:	Joonsoo Kim <iamjoonsoo.kim@....com>
Cc:	Andrew Morton <akpm@...ux-foundation.org>,
	Rik van Riel <riel@...hat.com>, Mel Gorman <mgorman@...e.de>,
	Michal Hocko <mhocko@...e.cz>,
	"Aneesh Kumar K.V" <aneesh.kumar@...ux.vnet.ibm.com>,
	KAMEZAWA Hiroyuki <kamezawa.hiroyu@...fujitsu.com>,
	Hugh Dickins <hughd@...gle.com>,
	Davidlohr Bueso <davidlohr.bueso@...com>,
	David Gibson <david@...son.dropbear.id.au>, linux-mm@...ck.org,
	linux-kernel@...r.kernel.org, Joonsoo Kim <js1304@...il.com>,
	Wanpeng Li <liwanp@...ux.vnet.ibm.com>,
	Hillf Danton <dhillf@...il.com>
Subject: Re: [PATCH 15/18] mm, hugetlb: move up anon_vma_prepare()

On Mon, Jul 29, 2013 at 03:05:37PM -0400, Naoya Horiguchi wrote:
> On Mon, Jul 29, 2013 at 02:32:06PM +0900, Joonsoo Kim wrote:
> > If we fail with a allocated hugepage, it is hard to recover properly.
> > One such example is reserve count. We don't have any method to recover
> > reserve count. Although, I will introduce a function to recover reserve
> > count in following patch, it is better not to allocate a hugepage
> > as much as possible. So move up anon_vma_prepare() which can be failed
> > in OOM situation.
> > 
> > Signed-off-by: Joonsoo Kim <iamjoonsoo.kim@....com>
> 
> Reviewed-by: Naoya Horiguchi <n-horiguchi@...jp.nec.com>

Sorry, let me suspend this Reviewed for a question.
If alloc_huge_page failed after we succeeded anon_vma_parepare,
the allocated anon_vma_chain and/or anon_vma are safely freed?
Or don't we have to free them?

Thanks,
Naoya Horiguchi

> > diff --git a/mm/hugetlb.c b/mm/hugetlb.c
> > index 683fd38..bb8a45f 100644
> > --- a/mm/hugetlb.c
> > +++ b/mm/hugetlb.c
> > @@ -2536,6 +2536,15 @@ retry_avoidcopy:
> >  	/* Drop page_table_lock as buddy allocator may be called */
> >  	spin_unlock(&mm->page_table_lock);
> >  
> > +	/*
> > +	 * When the original hugepage is shared one, it does not have
> > +	 * anon_vma prepared.
> > +	 */
> > +	if (unlikely(anon_vma_prepare(vma))) {
> > +		ret = VM_FAULT_OOM;
> > +		goto out_old_page;
> > +	}
> > +
> >  	use_reserve = vma_has_reserves(h, vma, address);
> >  	if (use_reserve == -ENOMEM) {
> >  		ret = VM_FAULT_OOM;
> > @@ -2590,15 +2599,6 @@ retry_avoidcopy:
> >  		goto out_lock;
> >  	}
> >  
> > -	/*
> > -	 * When the original hugepage is shared one, it does not have
> > -	 * anon_vma prepared.
> > -	 */
> > -	if (unlikely(anon_vma_prepare(vma))) {
> > -		ret = VM_FAULT_OOM;
> > -		goto out_new_page;
> > -	}
> > -
> >  	copy_user_huge_page(new_page, old_page, address, vma,
> >  			    pages_per_huge_page(h));
> >  	__SetPageUptodate(new_page);
> > @@ -2625,7 +2625,6 @@ retry_avoidcopy:
> >  	spin_unlock(&mm->page_table_lock);
> >  	mmu_notifier_invalidate_range_end(mm, mmun_start, mmun_end);
> >  
> > -out_new_page:
> >  	page_cache_release(new_page);
> >  out_old_page:
> >  	page_cache_release(old_page);
> > -- 
> > 1.7.9.5
> > 
> > --
> > To unsubscribe, send a message with 'unsubscribe linux-mm' in
> > the body to majordomo@...ck.org.  For more info on Linux MM,
> > see: http://www.linux-mm.org/ .
> > Don't email: <a href=mailto:"dont@...ck.org"> email@...ck.org </a>
> >
> 
> --
> To unsubscribe, send a message with 'unsubscribe linux-mm' in
> the body to majordomo@...ck.org.  For more info on Linux MM,
> see: http://www.linux-mm.org/ .
> Don't email: <a href=mailto:"dont@...ck.org"> email@...ck.org </a>
>
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/