Re: [PATCH] mm: constify oom_control, scan_control, and alloc_context nodemask

From: SeongJae Park

Date: Tue Jun 09 2026 - 20:23:04 EST


On Mon, 8 Jun 2026 20:29:19 -0400 Gregory Price <gourry@xxxxxxxxxx> wrote:

> The nodemasks in these structures may come from a variety of sources,
> including tasks and cpusets - and should never be modified by any code
> when being passed around inside another context.

Nice work, I also confirmed I can built the kernel with this patch.

>
> Signed-off-by: Gregory Price <gourry@xxxxxxxxxx>

Tested-by: SeongJae Park <sj@xxxxxxxxxx>
Acked-by: SeongJae Park <sj@xxxxxxxxxx>

[...]
> /*
> * The memory cgroup that hit its limit and as a result is the
> @@ -6599,7 +6599,7 @@ static bool allow_direct_reclaim(pg_data_t *pgdat)
> * happens, the page allocator should not consider triggering the OOM killer.
> */
> static bool throttle_direct_reclaim(gfp_t gfp_mask, struct zonelist *zonelist,
> - nodemask_t *nodemask)
> + const nodemask_t *nodemask)

Seems the above indentation has changed for a rason that I have no clue, and
also introduced a line having both spaces and tabs.

Just thinking loud.


Thanks,
SJ

[...]