From: Tejun Heo <tj@kernel.org>
To: zijun_hu@htc.com
Cc: akpm@linux-foundation.org, kuleshovmail@gmail.com,
ard.biesheuvel@linaro.org, tangchen@cn.fujitsu.com,
weiyang@linux.vnet.ibm.com, dev@g0hl1n.net,
david@gibson.dropbear.id.au, linux-mm@kvack.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] mm/memblock.c: fix index adjustment error in __next_mem_range_rev()
Date: Mon, 25 Jul 2016 14:52:18 -0400 [thread overview]
Message-ID: <20160725185218.GG19588@mtj.duckdns.org> (raw)
In-Reply-To: <42A378E55677204FAE257FE7EED241CB7E8EF004@CN-MBX01.HTC.COM.TW>
On Mon, Jul 25, 2016 at 07:34:12AM +0000, zijun_hu@htc.com wrote:
> Hi All,
> There is a bug in mm/memblock.c
> Could you review and phase-in this patch?
> Thanks a lot
>
> From 3abf1822d30f77f126bd7a3c09bb243d9c17a029 Mon Sep 17 00:00:00 2001
> From: zijun_hu <zijun_hu@htc.com>
> Date: Mon, 25 Jul 2016 15:06:57 +0800
> Subject: [PATCH] mm/memblock.c: fix index adjustment error in
> __next_mem_range_rev()
>
> fix region index adjustment error when parameter type_b of
> __next_mem_range_rev() == NULL
>
> Signed-off-by: zijun_hu <zijun_hu@htc.com>
> ---
> mm/memblock.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/mm/memblock.c b/mm/memblock.c
> index ac12489..b14973e 100644
> --- a/mm/memblock.c
> +++ b/mm/memblock.c
> @@ -1024,7 +1024,7 @@ void __init_memblock __next_mem_range_rev(u64 *idx, int nid, ulong flags,
> *out_end = m_end;
> if (out_nid)
> *out_nid = m_nid;
> - idx_a++;
> + idx_a--;
Looks good to me. Do you happen to have a test case for this bug?
Thanks.
--
tejun
--
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>
next prev parent reply other threads:[~2016-07-25 18:52 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-25 7:34 [PATCH] mm/memblock.c: fix index adjustment error in __next_mem_range_rev() zijun_hu
2016-07-25 18:52 ` Tejun Heo [this message]
2016-07-26 15:03 ` zijun_hu
2016-07-26 16:50 ` Tejun Heo
2016-07-26 15:09 ` 答复: " zijun_hu
-- strict thread matches above, loose matches on Subject: below --
2016-07-27 6:49 zijun_hu
2016-07-27 17:36 ` Tejun Heo
2016-07-27 7:12 zijun_hu
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=20160725185218.GG19588@mtj.duckdns.org \
--to=tj@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=ard.biesheuvel@linaro.org \
--cc=david@gibson.dropbear.id.au \
--cc=dev@g0hl1n.net \
--cc=kuleshovmail@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=tangchen@cn.fujitsu.com \
--cc=weiyang@linux.vnet.ibm.com \
--cc=zijun_hu@htc.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).