From: Vlastimil Babka <vbabka@suse.cz>
To: Wen Yang <wen.yang99@zte.com.cn>, linux-mm@kvack.org
Cc: akpm@linux-foundation.org, mhocko@suse.com,
kirill.shutemov@linux.intel.com, hannes@cmpxchg.org,
linux-kernel@vger.kernel.org, jiang.biao2@zte.com.cn
Subject: Re: [PATCH] mm/vmstat: fix divide error at __fragmentation_index
Date: Thu, 3 Aug 2017 10:09:59 +0200 [thread overview]
Message-ID: <1f3450b4-a48c-bac6-19ee-c0f5b4d4ce86@suse.cz> (raw)
In-Reply-To: <1501747181-30322-1-git-send-email-wen.yang99@zte.com.cn>
Hi,
On 08/03/2017 09:59 AM, Wen Yang wrote:
> From: Jiang Biao <jiang.biao2@zte.com.cn>
>
> When order is -1 or too big, *1UL << order* will be 0, which will
> cause divide error like this,
>
> divide error: 0000 [#1] SMP
> Call Trace:
> [<ffffffff81168423>] compaction_suitable+0x63/0xc0
> [<ffffffff81168a75>] compact_zone+0x35/0x950
> [<ffffffff811745b5>] ? free_percpu+0xb5/0x140
> [<ffffffff81092b23>] ? schedule_on_each_cpu+0x133/0x160
> [<ffffffff8116949c>] compact_node+0x10c/0x120
> [<ffffffff8116953c>] sysctl_compaction_handler+0x5c/0x90
> [<ffffffff811fa517>] proc_sys_call_handler+0x97/0xd0
> [<ffffffff811fa564>] proc_sys_write+0x14/0x20
> [<ffffffff81187368>] vfs_write+0xb8/0x1a0
> [<ffffffff81187c61>] sys_write+0x51/0x90
> [<ffffffff8100b052>] system_call_fastpath+0x16/0x1b
The trace seems to be from an old and non-mainline kernel, as it's the
same as you reported here:
https://bugzilla.kernel.org/show_bug.cgi?id=196555
In current mainline it seems to me that all callers of
__fragmentation_index() will only do so with a valid order.
I wouldn't mind making a non-hotpath code more robust, but probably in a
more obvious and self-reporting/documented way e.g. something like
if (WARN_ON_ONCE(order >= MAX_ORDER))
return 0;
> Signed-off-by: Wen Yang <wen.yang99@zte.com.cn>
> Reviewed-by: Jiang Biao <jiang.biao2@zte.com.cn>
> ---
> mm/vmstat.c | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/mm/vmstat.c b/mm/vmstat.c
> index 76f7367..2f9d012 100644
> --- a/mm/vmstat.c
> +++ b/mm/vmstat.c
> @@ -870,6 +870,9 @@ static int __fragmentation_index(unsigned int order, struct contig_page_info *in
> {
> unsigned long requested = 1UL << order;
>
> + if (!requested)
> + return 0;
Seems the indentation is broken here (spaces vs tabs).
Thanks,
Vlastimil
> +
> if (!info->free_blocks_total)
> return 0;
>
>
--
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:[~2017-08-03 8:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-03 7:59 [PATCH] mm/vmstat: fix divide error at __fragmentation_index Wen Yang
2017-08-03 8:09 ` Vlastimil Babka [this message]
-- strict thread matches above, loose matches on Subject: below --
2017-08-03 8:46 jiang.biao2
2017-08-03 9:12 Wen Yang
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=1f3450b4-a48c-bac6-19ee-c0f5b4d4ce86@suse.cz \
--to=vbabka@suse.cz \
--cc=akpm@linux-foundation.org \
--cc=hannes@cmpxchg.org \
--cc=jiang.biao2@zte.com.cn \
--cc=kirill.shutemov@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@suse.com \
--cc=wen.yang99@zte.com.cn \
/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).