Linux-mm Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Michal Koutný" <mkoutny@suse.com>
To: Ridong Chen <ridong.chen@linux.dev>
Cc: sashiko-reviews@lists.linux.dev, tj@kernel.org,
	hannes@cmpxchg.org,
	 "open list:CONTROL GROUP - MEMORY RESOURCE CONTROLLER (MEMCG)"
	<linux-mm@kvack.org>
Subject: Re: [RFC PATCH] mm/mglru: fix ineffective memory protection for non-kswapd reclaim
Date: Thu, 27 Aug 2026 11:26:45 +0200	[thread overview]
Message-ID: <apABJglqDFcB02VO@localhost.localdomain> (raw)
In-Reply-To: <0c606cf9-2b5a-4549-8ab1-0be619487412@linux.dev>

[-- Attachment #1: Type: text/plain, Size: 1232 bytes --]

Hi Ridong.

On Thu, Aug 27, 2026 at 09:29:13AM +0800, Ridong Chen <ridong.chen@linux.dev> wrote:
> On 8/26/2026 9:47 PM, sashiko-bot@kernel.org wrote:
> > Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
> > 
> > Pre-existing issues:
> > - [High] Integer overflow in `effective_protection()` calculations on systems with >= 16TB RAM.
> > --
> > 
> 
> Thanks for the careful analysis. You're right that this is pre-existing in
> effective_protection() and not introduced by this patch.
> 
> I'm not sure it's worth fixing in practice, though — the overflow requires
> systems with >= 16TB of RAM, which I've never encountered
> myself. So I'd rather not fold a fix for it into this patch.
> 
> I'd like to hear the maintainers' thoughts on whether this is worth
> addressing separately.

Machines with >=16 TiB aren't completely out of reach [1]. Then
configuring such protections to attain the overflow is another
condition, so I'd consider this a nice to have but not a
pressing fixup (separately, with thorough review of occurences where
total page counts/bytes might get multiplied).

HTH,
Michal

[1] E.g. https://aws.amazon.com/ec2/instance-types/u7i/

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 265 bytes --]

  parent reply	other threads:[~2026-08-27  9:26 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-26 13:30 [RFC PATCH] mm/mglru: fix ineffective memory protection for non-kswapd reclaim Ridong Chen
2026-08-27  1:37 ` Ridong Chen
     [not found] ` <20260826134733.051941F000E9@smtp.kernel.org>
     [not found]   ` <0c606cf9-2b5a-4549-8ab1-0be619487412@linux.dev>
2026-08-27  9:26     ` Michal Koutný [this message]
2026-08-28  1:49       ` Ridong Chen
2026-08-27 17:21 ` Johannes Weiner
2026-08-28  1:51   ` Ridong Chen

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=apABJglqDFcB02VO@localhost.localdomain \
    --to=mkoutny@suse.com \
    --cc=hannes@cmpxchg.org \
    --cc=linux-mm@kvack.org \
    --cc=ridong.chen@linux.dev \
    --cc=sashiko-reviews@lists.linux.dev \
    --cc=tj@kernel.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox