All of lore.kernel.org
 help / color / mirror / Atom feed
From: Vlastimil Babka <vbabka@suse.cz>
To: Andrew Morton <akpm@linux-foundation.org>,
	Xishi Qiu <qiuxishi@huawei.com>
Cc: Joonsoo Kim <js1304@gmail.com>,
	David Rientjes <rientjes@google.com>,
	Naoya Horiguchi <n-horiguchi@ah.jp.nec.com>,
	Laura Abbott <lauraa@codeaurora.org>,
	zhuhui@xiaomi.com, wangxq10@lzu.edu.cn,
	Linux MM <linux-mm@kvack.org>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] mm: fix invalid node in alloc_migrate_target()
Date: Thu, 31 Mar 2016 15:13:41 +0200	[thread overview]
Message-ID: <56FD2285.4080600@suse.cz> (raw)
In-Reply-To: <56FA7DC8.4000902@suse.cz>

On 03/29/2016 03:06 PM, Vlastimil Babka wrote:
> On 03/25/2016 08:22 PM, Andrew Morton wrote:
>> Also, mm/mempolicy.c:offset_il_node() worries me:
>>
>> 	do {
>> 		nid = next_node(nid, pol->v.nodes);
>> 		c++;
>> 	} while (c <= target);
>>
>> Can't `nid' hit MAX_NUMNODES?
>
> AFAICS it can. interleave_nid() uses this and the nid is then used e.g.
> in node_zonelist() where it's used for NODE_DATA(nid). That's quite
> scary. It also predates git. Why don't we see crashes or KASAN finding this?

Ah, I see. In offset_il_node(), nid is initialized to -1, and the number 
of do-while iterations calling next_node() is up to the number of bits 
set in the pol->v.nodes bitmap, so it can't reach past the last set bit 
and return MAX_NUMNODES.

--
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: Vlastimil Babka <vbabka@suse.cz>
To: Andrew Morton <akpm@linux-foundation.org>,
	Xishi Qiu <qiuxishi@huawei.com>
Cc: Joonsoo Kim <js1304@gmail.com>,
	David Rientjes <rientjes@google.com>,
	Naoya Horiguchi <n-horiguchi@ah.jp.nec.com>,
	Laura Abbott <lauraa@codeaurora.org>,
	zhuhui@xiaomi.com, wangxq10@lzu.edu.cn,
	Linux MM <linux-mm@kvack.org>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] mm: fix invalid node in alloc_migrate_target()
Date: Thu, 31 Mar 2016 15:13:41 +0200	[thread overview]
Message-ID: <56FD2285.4080600@suse.cz> (raw)
In-Reply-To: <56FA7DC8.4000902@suse.cz>

On 03/29/2016 03:06 PM, Vlastimil Babka wrote:
> On 03/25/2016 08:22 PM, Andrew Morton wrote:
>> Also, mm/mempolicy.c:offset_il_node() worries me:
>>
>> 	do {
>> 		nid = next_node(nid, pol->v.nodes);
>> 		c++;
>> 	} while (c <= target);
>>
>> Can't `nid' hit MAX_NUMNODES?
>
> AFAICS it can. interleave_nid() uses this and the nid is then used e.g.
> in node_zonelist() where it's used for NODE_DATA(nid). That's quite
> scary. It also predates git. Why don't we see crashes or KASAN finding this?

Ah, I see. In offset_il_node(), nid is initialized to -1, and the number 
of do-while iterations calling next_node() is up to the number of bits 
set in the pol->v.nodes bitmap, so it can't reach past the last set bit 
and return MAX_NUMNODES.

  reply	other threads:[~2016-03-31 13:13 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-25  6:56 [PATCH] mm: fix invalid node in alloc_migrate_target() Xishi Qiu
2016-03-25  6:56 ` Xishi Qiu
2016-03-25 19:22 ` Andrew Morton
2016-03-25 19:22   ` Andrew Morton
2016-03-26  5:31   ` Xishi Qiu
2016-03-26  5:31     ` Xishi Qiu
2016-03-29  9:52     ` Vlastimil Babka
2016-03-29  9:52       ` Vlastimil Babka
2016-03-29 10:06       ` Vlastimil Babka
2016-03-29 10:06         ` Vlastimil Babka
2016-03-29 10:37       ` Xishi Qiu
2016-03-29 10:37         ` Xishi Qiu
2016-03-29 12:21         ` Vlastimil Babka
2016-03-29 12:21           ` Vlastimil Babka
2016-03-29 13:06   ` Vlastimil Babka
2016-03-29 13:06     ` Vlastimil Babka
2016-03-31 13:13     ` Vlastimil Babka [this message]
2016-03-31 13:13       ` Vlastimil Babka
2016-03-31 21:01       ` Andrew Morton
2016-03-31 21:01         ` Andrew Morton
2016-04-01  8:42         ` Vlastimil Babka
2016-04-01  8:42           ` Vlastimil Babka
2016-03-29 15:52   ` Michal Hocko
2016-03-29 15:52     ` Michal Hocko
2016-03-29 12:25 ` Vlastimil Babka
2016-03-29 12:25   ` Vlastimil Babka
2016-03-30  1:13   ` Naoya Horiguchi
2016-03-30  1:13     ` Naoya Horiguchi

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=56FD2285.4080600@suse.cz \
    --to=vbabka@suse.cz \
    --cc=akpm@linux-foundation.org \
    --cc=js1304@gmail.com \
    --cc=lauraa@codeaurora.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=n-horiguchi@ah.jp.nec.com \
    --cc=qiuxishi@huawei.com \
    --cc=rientjes@google.com \
    --cc=wangxq10@lzu.edu.cn \
    --cc=zhuhui@xiaomi.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.