All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mel Gorman <mgorman@suse.de>
To: Dave Hansen <dave@linux.vnet.ibm.com>
Cc: akpm@osdl.org, linux-kernel@vger.kernel.org,
	torvalds@linux-foundation.org, linux-mm@kvack.org
Subject: Re: [PATCH] mm: compaction: Fix return value of capture_free_page
Date: Tue, 27 Nov 2012 11:07:47 +0000	[thread overview]
Message-ID: <20121127110746.GN8218@suse.de> (raw)
In-Reply-To: <50B3858D.2060404@linux.vnet.ibm.com>

On Mon, Nov 26, 2012 at 07:06:53AM -0800, Dave Hansen wrote:
> On 11/26/2012 03:23 AM, Mel Gorman wrote:
> > On Wed, Nov 21, 2012 at 02:21:51PM -0500, Dave Hansen wrote:
> >>
> >> This needs to make it in before 3.7 is released.
> >>
> > 
> > This is also required. Dave, can you double check? The surprise is that
> > this does not blow up very obviously.
> ...
> > @@ -1422,7 +1422,7 @@ int capture_free_page(struct page *page, int alloc_order, int migratetype)
> >  		}
> >  	}
> > 
> > -	return 1UL << order;
> > +	return 1UL << alloc_order;
> >  }
> 
> compact_capture_page() only looks at the boolean return value out of
> capture_free_page(), so it wouldn't notice.  split_free_page() does.
> But, when it calls capture_free_page(), order==alloc_order, so it
> wouldn't make a difference.  So, there's probably no actual bug here,
> but it's certainly a wrong return value.
> 

I don't think it is fine in this case.

isolate_freepages_block
isolated = split_free_page(page);
  -> split_free_page
     nr_pages = capture_free_page(page, order, 0);
     -> capture_free_page (returns wrong value of too many pages)
     return nr_pages;

so now isolate_freepages_block has the wrong value with nr_pages holding
a value for a larger number of pages than are really isolated and does
this

                for (i = 0; i < isolated; i++) {
                        list_add(&page->lru, freelist);
                        page++;
                }

so potentially that is now adding pages that are already on the buddy list
to the local free list and "fun" ensues.

-- 
Mel Gorman
SUSE Labs

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

WARNING: multiple messages have this Message-ID (diff)
From: Mel Gorman <mgorman@suse.de>
To: Dave Hansen <dave@linux.vnet.ibm.com>
Cc: akpm@osdl.org, linux-kernel@vger.kernel.org,
	torvalds@linux-foundation.org, linux-mm@kvack.org
Subject: Re: [PATCH] mm: compaction: Fix return value of capture_free_page
Date: Tue, 27 Nov 2012 11:07:47 +0000	[thread overview]
Message-ID: <20121127110746.GN8218@suse.de> (raw)
In-Reply-To: <50B3858D.2060404@linux.vnet.ibm.com>

On Mon, Nov 26, 2012 at 07:06:53AM -0800, Dave Hansen wrote:
> On 11/26/2012 03:23 AM, Mel Gorman wrote:
> > On Wed, Nov 21, 2012 at 02:21:51PM -0500, Dave Hansen wrote:
> >>
> >> This needs to make it in before 3.7 is released.
> >>
> > 
> > This is also required. Dave, can you double check? The surprise is that
> > this does not blow up very obviously.
> ...
> > @@ -1422,7 +1422,7 @@ int capture_free_page(struct page *page, int alloc_order, int migratetype)
> >  		}
> >  	}
> > 
> > -	return 1UL << order;
> > +	return 1UL << alloc_order;
> >  }
> 
> compact_capture_page() only looks at the boolean return value out of
> capture_free_page(), so it wouldn't notice.  split_free_page() does.
> But, when it calls capture_free_page(), order==alloc_order, so it
> wouldn't make a difference.  So, there's probably no actual bug here,
> but it's certainly a wrong return value.
> 

I don't think it is fine in this case.

isolate_freepages_block
isolated = split_free_page(page);
  -> split_free_page
     nr_pages = capture_free_page(page, order, 0);
     -> capture_free_page (returns wrong value of too many pages)
     return nr_pages;

so now isolate_freepages_block has the wrong value with nr_pages holding
a value for a larger number of pages than are really isolated and does
this

                for (i = 0; i < isolated; i++) {
                        list_add(&page->lru, freelist);
                        page++;
                }

so potentially that is now adding pages that are already on the buddy list
to the local free list and "fun" ensues.

-- 
Mel Gorman
SUSE Labs

  reply	other threads:[~2012-11-27 11:07 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-21 19:21 [PATCH] [3.7-rc] fix incorrect NR_FREE_PAGES accounting (appears like memory leak) Dave Hansen
2012-11-21 19:21 ` Dave Hansen
2012-11-26 11:23 ` [PATCH] mm: compaction: Fix return value of capture_free_page Mel Gorman
2012-11-26 11:23   ` Mel Gorman
2012-11-26 15:06   ` Dave Hansen
2012-11-26 15:06     ` Dave Hansen
2012-11-27 11:07     ` Mel Gorman [this message]
2012-11-27 11:07       ` Mel Gorman

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20121127110746.GN8218@suse.de \
    --to=mgorman@suse.de \
    --cc=akpm@osdl.org \
    --cc=dave@linux.vnet.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=torvalds@linux-foundation.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.