From: Johannes Weiner <hannes@cmpxchg.org>
To: Jianlin Shi <shijianlin11@foxmail.com>
Cc: linux-mm@kvack.org, akpm@linux-foundation.org, vbabka@kernel.org,
surenb@google.com, mhocko@suse.com, jackmanb@google.com,
ziy@nvidia.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v5] mm/page_alloc: only update lowmem_reserve_ratio on sysctl write
Date: Thu, 6 Aug 2026 09:50:16 -0400 [thread overview]
Message-ID: <anSRGASe5FIrqwlg@cmpxchg.org> (raw)
In-Reply-To: <tencent_A860C873956A52E26AD8D309A308A241BA08@qq.com>
On Thu, Aug 06, 2026 at 04:27:34PM +0800, Jianlin Shi wrote:
> lowmem_reserve_ratio_sysctl_handler() ignores the return value of
> proc_dointvec_minmax() and always calls setup_per_zone_lowmem_reserve(),
> even for read operations.
>
> Fix three issues:
>
> 1. Propagate errors from proc_dointvec_minmax() instead of always
> returning success. For example, writing non-integer garbage to the
> sysctl now returns an error instead of silently succeeding with
> unchanged values.
>
> 2. Only call setup_per_zone_lowmem_reserve() when the sysctl is
> actually written, matching the write-only refresh pattern of
> min_free_kbytes and watermark_scale_factor handlers.
>
> 3. On write, parse into a temporary ratio[] array and only copy into
> sysctl_lowmem_reserve_ratio[] and refresh derived state after the
> full vector is validated. This avoids leaving the ratio array
> partially updated while skipping setup when proc_dointvec_minmax()
> returns an error on a later element (suggested by Andrew Morton).
>
> Drop the manual "< 1 -> 0" sanitization loop and set .extra1 =
> SYSCTL_ZERO on the ctl_table entry so proc_dointvec_minmax() enforces
> the minimum on write; negative values now return -EINVAL instead of
> being silently coerced to 0 (suggested by Vlastimil Babka).
>
> Link: https://lore.kernel.org/linux-mm/tencent_FFD4F4D728AAE8A8AE0AF277A59854A29A06@qq.com/
>
> Signed-off-by: Jianlin Shi <shijianlin11@foxmail.com>
> ---
> Changes in v5:
> - Size temporary ratio[] with ARRAY_SIZE(sysctl_lowmem_reserve_ratio)
> (Andrew Morton)
>
> Changes in v4:
> - Parse writes into a temporary ratio[] array; commit and setup only on
> full success (Andrew Morton)
> - Update handler comment: proc_dointvec_minmax() and write-only setup
>
> Changes in v3:
> - Rewrite commit log to focus on the two tangible fixes as suggested by
> Johannes Weiner.
>
> Changes in v2:
> - Add .extra1 = SYSCTL_ZERO to ctl_table entry
> - Remove manual sanitization loop; negative writes now return -EINVAL
>
> v1: https://lore.kernel.org/linux-mm/tencent_FFD4F4D728AAE8A8AE0AF277A59854A29A06@qq.com/
>
> mm/page_alloc.c | 24 ++++++++++++++++--------
> 1 file changed, 16 insertions(+), 8 deletions(-)
>
> diff --git a/mm/page_alloc.c b/mm/page_alloc.c
> index 0387d2afd535..51f35e44132a 100644
> --- a/mm/page_alloc.c
> +++ b/mm/page_alloc.c
> @@ -6673,8 +6673,8 @@ static int sysctl_min_slab_ratio_sysctl_handler(const struct ctl_table *table, i
>
> /*
> * lowmem_reserve_ratio_sysctl_handler - just a wrapper around
> - * proc_dointvec() so that we can call setup_per_zone_lowmem_reserve()
> - * whenever sysctl_lowmem_reserve_ratio changes.
> + * proc_dointvec_minmax() so that we can call
> + * setup_per_zone_lowmem_reserve() when the sysctl is written.
> *
> * The reserve ratio obviously has absolutely no relation with the
> * minimum watermarks. The lowmem reserve ratio can only make sense
> @@ -6683,16 +6683,23 @@ static int sysctl_min_slab_ratio_sysctl_handler(const struct ctl_table *table, i
> static int lowmem_reserve_ratio_sysctl_handler(const struct ctl_table *table,
> int write, void *buffer, size_t *length, loff_t *ppos)
> {
> - int i;
> + struct ctl_table tmp = *table;
> + int ratio[ARRAY_SIZE(sysctl_lowmem_reserve_ratio)];
> + int rc;
>
> - proc_dointvec_minmax(table, write, buffer, length, ppos);
> + if (!write)
> + return proc_dointvec_minmax(table, write, buffer, length, ppos);
>
> - for (i = 0; i < MAX_NR_ZONES; i++) {
> - if (sysctl_lowmem_reserve_ratio[i] < 1)
> - sysctl_lowmem_reserve_ratio[i] = 0;
> - }
This could use a comment. How about:
/*
* proc_dointvec_max() works incrementally. Use a buffer
* and only set the values if all of them parse cleanly.
*/
> + memcpy(ratio, sysctl_lowmem_reserve_ratio, sizeof(ratio));
> + tmp.data = ratio;
>
> + rc = proc_dointvec_minmax(&tmp, write, buffer, length, ppos);
> + if (rc)
> + return rc;
> +
> + memcpy(sysctl_lowmem_reserve_ratio, ratio, sizeof(ratio));
> setup_per_zone_lowmem_reserve();
But otherwise, looks good to me now.
Acked-by: Johannes Weiner <hannes@cmpxchg.org>
next prev parent reply other threads:[~2026-08-06 13:50 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-28 10:32 [PATCH] mm/page_alloc: only update lowmem_reserve_ratio on sysctl write Jianlin Shi
2026-07-30 15:28 ` Vlastimil Babka (SUSE)
2026-07-31 3:36 ` Jianlin Shi
2026-07-31 3:42 ` [PATCH v2] " Jianlin Shi
2026-07-31 8:06 ` Vlastimil Babka (SUSE)
2026-08-01 7:36 ` Johannes Weiner
2026-08-01 15:11 ` [PATCH v3] " Jianlin Shi
2026-08-01 18:44 ` Andrew Morton
2026-08-02 14:31 ` Jianlin Shi
2026-08-03 8:27 ` Vlastimil Babka (SUSE)
2026-08-04 12:20 ` Joel Granados
2026-08-04 14:33 ` Vlastimil Babka (SUSE)
2026-08-06 8:27 ` Joel Granados
2026-08-02 14:57 ` [PATCH v4] " Jianlin Shi
2026-08-04 0:48 ` Andrew Morton
2026-08-06 7:32 ` Jianlin Shi
2026-08-06 8:27 ` [PATCH v5] " Jianlin Shi
2026-08-06 13:50 ` Johannes Weiner [this message]
2026-08-06 21:20 ` Andrew Morton
2026-08-07 9:45 ` Joel Granados
2026-08-07 10:05 ` Vlastimil Babka (SUSE)
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=anSRGASe5FIrqwlg@cmpxchg.org \
--to=hannes@cmpxchg.org \
--cc=akpm@linux-foundation.org \
--cc=jackmanb@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@suse.com \
--cc=shijianlin11@foxmail.com \
--cc=surenb@google.com \
--cc=vbabka@kernel.org \
--cc=ziy@nvidia.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.