Re: [PATCH v2] mm/cma: fix alloc_contig_range ret code/potential leak

2017-11-28 Thread Joonsoo Kim
On Wed, Nov 22, 2017 at 10:52:14AM -0800, Mike Kravetz wrote: > If the call __alloc_contig_migrate_range() in alloc_contig_range > returns -EBUSY, processing continues so that test_pages_isolated() > is called where there is a tracepoint to identify the busy pages. > However, it is possible for

Re: [PATCH v2] mm/cma: fix alloc_contig_range ret code/potential leak

2017-11-28 Thread Joonsoo Kim
On Wed, Nov 22, 2017 at 10:52:14AM -0800, Mike Kravetz wrote: > If the call __alloc_contig_migrate_range() in alloc_contig_range > returns -EBUSY, processing continues so that test_pages_isolated() > is called where there is a tracepoint to identify the busy pages. > However, it is possible for

Re: [PATCH v2] mm/cma: fix alloc_contig_range ret code/potential leak

2017-11-27 Thread Johannes Weiner
On Wed, Nov 22, 2017 at 10:52:14AM -0800, Mike Kravetz wrote: > If the call __alloc_contig_migrate_range() in alloc_contig_range > returns -EBUSY, processing continues so that test_pages_isolated() > is called where there is a tracepoint to identify the busy pages. > However, it is possible for

Re: [PATCH v2] mm/cma: fix alloc_contig_range ret code/potential leak

2017-11-27 Thread Johannes Weiner
On Wed, Nov 22, 2017 at 10:52:14AM -0800, Mike Kravetz wrote: > If the call __alloc_contig_migrate_range() in alloc_contig_range > returns -EBUSY, processing continues so that test_pages_isolated() > is called where there is a tracepoint to identify the busy pages. > However, it is possible for

Re: [PATCH v2] mm/cma: fix alloc_contig_range ret code/potential leak

2017-11-23 Thread Michal Hocko
On Wed 22-11-17 10:52:14, Mike Kravetz wrote: > If the call __alloc_contig_migrate_range() in alloc_contig_range > returns -EBUSY, processing continues so that test_pages_isolated() > is called where there is a tracepoint to identify the busy pages. > However, it is possible for busy pages to

Re: [PATCH v2] mm/cma: fix alloc_contig_range ret code/potential leak

2017-11-23 Thread Michal Hocko
On Wed 22-11-17 10:52:14, Mike Kravetz wrote: > If the call __alloc_contig_migrate_range() in alloc_contig_range > returns -EBUSY, processing continues so that test_pages_isolated() > is called where there is a tracepoint to identify the busy pages. > However, it is possible for busy pages to

Re: [PATCH v2] mm/cma: fix alloc_contig_range ret code/potential leak

2017-11-23 Thread Vlastimil Babka
On 11/22/2017 07:52 PM, Mike Kravetz wrote: > If the call __alloc_contig_migrate_range() in alloc_contig_range > returns -EBUSY, processing continues so that test_pages_isolated() > is called where there is a tracepoint to identify the busy pages. > However, it is possible for busy pages to become

Re: [PATCH v2] mm/cma: fix alloc_contig_range ret code/potential leak

2017-11-23 Thread Vlastimil Babka
On 11/22/2017 07:52 PM, Mike Kravetz wrote: > If the call __alloc_contig_migrate_range() in alloc_contig_range > returns -EBUSY, processing continues so that test_pages_isolated() > is called where there is a tracepoint to identify the busy pages. > However, it is possible for busy pages to become

[PATCH v2] mm/cma: fix alloc_contig_range ret code/potential leak

2017-11-22 Thread Mike Kravetz
If the call __alloc_contig_migrate_range() in alloc_contig_range returns -EBUSY, processing continues so that test_pages_isolated() is called where there is a tracepoint to identify the busy pages. However, it is possible for busy pages to become available between the calls to these two routines.

[PATCH v2] mm/cma: fix alloc_contig_range ret code/potential leak

2017-11-22 Thread Mike Kravetz
If the call __alloc_contig_migrate_range() in alloc_contig_range returns -EBUSY, processing continues so that test_pages_isolated() is called where there is a tracepoint to identify the busy pages. However, it is possible for busy pages to become available between the calls to these two routines.