From: Mel Gorman <mgorman@techsingularity.net>
To: yalin wang <yalin.wang2010@gmail.com>
Cc: akpm@linux-foundation.org, vbabka@suse.cz, mhocko@suse.com,
rientjes@google.com, js1304@gmail.com,
kirill.shutemov@linux.intel.com, hannes@cmpxchg.org,
alexander.h.duyck@redhat.com, linux-mm@kvack.org,
linux-kernel@vger.kernel.org
Subject: Re: [RFC] mm: fix a BUG, the page is allocated 2 times
Date: Mon, 12 Oct 2015 14:52:50 +0100 [thread overview]
Message-ID: <20151012135250.GA3625@techsingularity.net> (raw)
In-Reply-To: <1444617606-8685-1-git-send-email-yalin.wang2010@gmail.com>
On Mon, Oct 12, 2015 at 10:40:06AM +0800, yalin wang wrote:
> Remove unlikely(order), because we are sure order is not zero if
> code reach here, also add if (page == NULL), only allocate page again if
> __rmqueue_smallest() failed or alloc_flags & ALLOC_HARDER == 0
>
> Signed-off-by: yalin wang <yalin.wang2010@gmail.com>
Thanks very much for catching this!
Acked-by: Mel Gorman <mgorman@techsingularity.net>
With your current subject and changelog, there is a small risk that Andrew
will miss this or not see it for some time. Would you mind resending the
patch with a changelog similar to this please? It spells out that it is
a fix to an mmotm patch so it'll be obvious where it should be inserted
before merging to mainline.
From: yalin wang <yalin.wang2010@gmail.com>
Subject: [PATCH] mm, page_alloc: reserve pageblocks for high-order atomic allocations on demand -fix
There is a redundant check and a memory leak introduced by a patch in
mmotm. This patch removes an unlikely(order) check as we are sure order
is not zero at the time. It also checks if a page is already allocated
to avoid a memory leak.
This is a fix to the mmotm patch
mm-page_alloc-reserve-pageblocks-for-high-order-atomic-allocations-on-demand.patch
Signed-off-by: yalin wang <yalin.wang2010@gmail.com>
Acked-by: Mel Gorman <mgorman@techsingularity.net>
--
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@techsingularity.net>
To: yalin wang <yalin.wang2010@gmail.com>
Cc: akpm@linux-foundation.org, vbabka@suse.cz, mhocko@suse.com,
rientjes@google.com, js1304@gmail.com,
kirill.shutemov@linux.intel.com, hannes@cmpxchg.org,
alexander.h.duyck@redhat.com, linux-mm@kvack.org,
linux-kernel@vger.kernel.org
Subject: Re: [RFC] mm: fix a BUG, the page is allocated 2 times
Date: Mon, 12 Oct 2015 14:52:50 +0100 [thread overview]
Message-ID: <20151012135250.GA3625@techsingularity.net> (raw)
In-Reply-To: <1444617606-8685-1-git-send-email-yalin.wang2010@gmail.com>
On Mon, Oct 12, 2015 at 10:40:06AM +0800, yalin wang wrote:
> Remove unlikely(order), because we are sure order is not zero if
> code reach here, also add if (page == NULL), only allocate page again if
> __rmqueue_smallest() failed or alloc_flags & ALLOC_HARDER == 0
>
> Signed-off-by: yalin wang <yalin.wang2010@gmail.com>
Thanks very much for catching this!
Acked-by: Mel Gorman <mgorman@techsingularity.net>
With your current subject and changelog, there is a small risk that Andrew
will miss this or not see it for some time. Would you mind resending the
patch with a changelog similar to this please? It spells out that it is
a fix to an mmotm patch so it'll be obvious where it should be inserted
before merging to mainline.
From: yalin wang <yalin.wang2010@gmail.com>
Subject: [PATCH] mm, page_alloc: reserve pageblocks for high-order atomic allocations on demand -fix
There is a redundant check and a memory leak introduced by a patch in
mmotm. This patch removes an unlikely(order) check as we are sure order
is not zero at the time. It also checks if a page is already allocated
to avoid a memory leak.
This is a fix to the mmotm patch
mm-page_alloc-reserve-pageblocks-for-high-order-atomic-allocations-on-demand.patch
Signed-off-by: yalin wang <yalin.wang2010@gmail.com>
Acked-by: Mel Gorman <mgorman@techsingularity.net>
next prev parent reply other threads:[~2015-10-12 13:52 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-12 2:40 [RFC] mm: fix a BUG, the page is allocated 2 times yalin wang
2015-10-12 2:40 ` yalin wang
2015-10-12 7:38 ` Vlastimil Babka
2015-10-12 7:38 ` Vlastimil Babka
2015-10-12 7:58 ` yalin wang
2015-10-12 7:58 ` yalin wang
2015-10-12 10:05 ` Kirill A. Shutemov
2015-10-12 10:05 ` Kirill A. Shutemov
2015-10-12 11:22 ` Vlastimil Babka
2015-10-12 11:22 ` Vlastimil Babka
2015-10-12 13:52 ` Mel Gorman [this message]
2015-10-12 13:52 ` Mel Gorman
2015-10-13 1:43 ` yalin wang
2015-10-13 1:43 ` yalin wang
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=20151012135250.GA3625@techsingularity.net \
--to=mgorman@techsingularity.net \
--cc=akpm@linux-foundation.org \
--cc=alexander.h.duyck@redhat.com \
--cc=hannes@cmpxchg.org \
--cc=js1304@gmail.com \
--cc=kirill.shutemov@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@suse.com \
--cc=rientjes@google.com \
--cc=vbabka@suse.cz \
--cc=yalin.wang2010@gmail.com \
/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.