[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <64E60F6F-7582-427B-8DD5-EF97B1656F5A@lca.pw>
Date: Fri, 8 Nov 2019 16:26:52 -0500
From: Qian Cai <cai@....pw>
To: akpm@...ux-foundation.org
Cc: mhocko@...e.com, hannes@...xchg.org, guro@...com,
linux-mm@...ck.org, cgroups@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH -next] mm/vmscan: fix an undefined behavior for zone id
> On Nov 8, 2019, at 3:44 PM, Qian Cai <cai@....pw> wrote:
>
> - for (zid = 0; zid <= zone_idx; zid++) {
> + for (zid = 0; zid < zone_idx; zid++) {
> struct zone *zone =
Oops, I think here needs to be,
for (zid = 0; zid <= zone_idx && zid < MAX_NR_ZONES; zid++) {
to deal with this MAX_NR_ZONES special case.
Powered by blists - more mailing lists