From: zijun_hu <zijun_hu@zoho.com>
To: Tejun Heo <tj@kernel.org>
Cc: zijun_hu@htc.com, Andrew Morton <akpm@linux-foundation.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
linux-mm@kvack.org, cl@linux.com
Subject: Re: [RESEND PATCH 1/1] mm/percpu.c: correct max_distance calculation for pcpu_embed_first_chunk()
Date: Thu, 29 Sep 2016 19:29:12 +0800 [thread overview]
Message-ID: <d17c5531-7a3b-7463-ba38-3a0eb8de0b84@zoho.com> (raw)
In-Reply-To: <20160929103507.GA25170@mtj.duckdns.org>
On 2016/9/29 18:35, Tejun Heo wrote:
> Hello,
>
> On Sat, Sep 24, 2016 at 07:20:49AM +0800, zijun_hu wrote:
>> it is error to represent the max range max_distance spanned by all the
>> group areas as the offset of the highest group area plus unit size in
>> pcpu_embed_first_chunk(), it should equal to the offset plus the size
>> of the highest group area
>>
>> in order to fix this issue,let us find the highest group area who has the
>> biggest base address among all the ones, then max_distance is formed by
>> add it's offset and size value
>
> [PATCH] percpu: fix max_distance calculation in pcpu_embed_first_chunk()
>
> pcpu_embed_first_chunk() calculates the range a percpu chunk spans
> into max_distance and uses it to ensure that a chunk is not too big
> compared to the total vmalloc area. However, during calculation, it
> used incorrect top address by adding a unit size to the higest
> group's base address.
>
> This can make the calculated max_distance slightly smaller than the
> actual distance although given the scale of values involved the error
> is very unlikely to have an actual impact.
>
> Fix this issue by adding the group's size instead of a unit size.
>
>> the type of variant max_distance is changed from size_t to unsigned long
>> to prevent potential overflow
>
> This doesn't make any sense. All the values involved are valid
> addresses (or +1 of it), they can't overflow and size_t is the same
> size as ulong.
>
>> @@ -2025,17 +2026,18 @@ int __init pcpu_embed_first_chunk(size_t reserved_size, size_t dyn_size,
>> }
>>
>> /* base address is now known, determine group base offsets */
>> - max_distance = 0;
>> + i = 0;
>> for (group = 0; group < ai->nr_groups; group++) {
>> ai->groups[group].base_offset = areas[group] - base;
>> - max_distance = max_t(size_t, max_distance,
>> - ai->groups[group].base_offset);
>> + if (areas[group] > areas[i])
>> + i = group;
>> }
>> - max_distance += ai->unit_size;
>> + max_distance = ai->groups[i].base_offset +
>> + (unsigned long)ai->unit_size * ai->groups[i].nr_units;
>
> I don't think you need ulong cast here.
>
> Thanks.
>
okay, thanks for your reply
i will correct this in another patch
--
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>
prev parent reply other threads:[~2016-09-29 11:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-23 18:20 [PATCH " zijun_hu
2016-09-23 19:23 ` Tejun Heo
2016-09-23 21:16 ` zijun_hu
2016-09-23 21:30 ` Tejun Heo
2016-09-23 23:20 ` [RESEND PATCH " zijun_hu
2016-09-29 10:35 ` Tejun Heo
2016-09-29 11:29 ` zijun_hu [this message]
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=d17c5531-7a3b-7463-ba38-3a0eb8de0b84@zoho.com \
--to=zijun_hu@zoho.com \
--cc=akpm@linux-foundation.org \
--cc=cl@linux.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=tj@kernel.org \
--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