Re: [PATCH -next] mm/vmscan: fix an undefined behavior for zone id

From: Chris Down
Date: Mon Nov 11 2019 - 08:14:32 EST


Chris Down writes:
Ah, I just saw this in my local checkout and thought it was from my changes, until I saw it's also on clean mmots checkout. Thanks for the fixup!

Also, does this mean we should change callers that may pass through zone_idx=MAX_NR_ZONES to become MAX_NR_ZONES-1 in a separate commit, then remove this interim fixup? I'm worried otherwise we might paper over real issues in future.