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, zhiyuan_zhu@htc.com
Subject: Re: [PATCH] mm/memblock.c: fix index adjustment error in __next_mem_range_rev()
Date: Tue, 26 Jul 2016 12:50:40 -0400 [thread overview]
Message-ID: <20160726165040.GU19588@mtj.duckdns.org> (raw)
In-Reply-To: <42A378E55677204FAE257FE7EED241CB7E8EF0C9@CN-MBX01.HTC.COM.TW>
Hello,
On Tue, Jul 26, 2016 at 03:03:58PM +0000, zijun_hu@htc.com wrote:
> I am sorry, I don't take any test for the patch attached in previous
> mail, and it can't fix the bug completely, please ignore it I
> provide a new patch attached in this mail which pass test and can
> fix the issue described below
>
> __next_mem_range_rev() defined in mm/memblock.c doesn't Achieve
> desired purpose if parameter type_b ==NULL This new patch can fix
> the issue and get the last reversed region contained in type_a
> rightly
Can you please flow future mails to 80 column?
> The new patch is descripted as follows
>
> From 0e242eda7696f176a9a2e585a1db01f0575b39c9 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
The patch is now fixing two bugs. It'd be nice to describe each in
the description and how the patch was tested.
> @@ -991,7 +991,11 @@ void __init_memblock __next_mem_range_rev(u64 *idx, int nid, ulong flags,
>
> if (*idx == (u64)ULLONG_MAX) {
> idx_a = type_a->cnt - 1;
> - idx_b = type_b->cnt;
> + /* in order to get the last reversed region rightly */
Before, it would trigger null deref. I don't think the above comment
is necessary.
> + if (type_b != NULL)
> + idx_b = type_b->cnt;
> + else
> + idx_b = 0;
> }
>
> for (; idx_a >= 0; idx_a--) {
> @@ -1024,7 +1028,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--;
> *idx = (u32)idx_a | (u64)idx_b << 32;
> return;
> }
Both changes look good to me. Provided the changes are tested,
Acked-by: Tejun Heo <tj@kernel.org>
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-26 16:50 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
2016-07-26 15:03 ` zijun_hu
2016-07-26 16:50 ` Tejun Heo [this message]
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=20160726165040.GU19588@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=zhiyuan_zhu@htc.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).