Linux-mm Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: SJ Park <sj@kernel.org>
To: Mark Polyakov <mark@thundercompute.com>
Cc: SJ Park <sj@kernel.org>,
	stable@vger.kernel.org, damon@lists.linux.dev,
	linux-mm@kvack.org
Subject: Re: Backport request for 6.12.y: mm/damon/reclaim: use parameter context correctly
Date: Mon, 16 Nov 2026 18:54:28 -0800	[thread overview]
Message-ID: <20261117025429.117165-1-sj@kernel.org> (raw)
In-Reply-To: <CAA5JH2yO-gw1gn_172hv0YWFfQpkXz915a=uoVH+e49P_D8-+Q@mail.gmail.com>

On Mon, 16 Nov 2026 18:39:08 -0800 Mark Polyakov <mark@thundercompute.com> wrote:

> Hi, would appreciate a backport to 6.12.y of the commit
> fed48693bdfeca666f7536ba88a05e9a4e5523b6 (mm/damon/reclaim: use
> parameter context correctly,
> https://git.kernel.org/torvalds/c/fed48693bdfeca666f7536ba88a05e9a4e5523b6).
> It seems 6.12 gets backports of most DAMON fixes but this one must
> have slipped through.
> 
> We've run into the issue fixed by the commit on 6.12.115: A guest VM
> with DAMON_RECLAIM enabled but no reclamation occurred. After
> backporting this fix ourselves, it started reclaiming.

Thank you for this issue report and requesting backport of the fix!

I just posted [1] the fix for 6.12.y.  I mentioned you on the comment of the
patch, but forgot Cc-ing you, sorry.  Please use the lore link to review.
Also, let me know if I did anything wrong while doing the porting.

[1] https://lore.kernel.org/20261117025144.117100-1-sj@kernel.org


Thanks,
SJ

[...]


      reply	other threads:[~2026-11-17  2:54 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-17  2:39 Backport request for 6.12.y: mm/damon/reclaim: use parameter context correctly Mark Polyakov
2026-11-17  2:54 ` SJ Park [this message]

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=20261117025429.117165-1-sj@kernel.org \
    --to=sj@kernel.org \
    --cc=damon@lists.linux.dev \
    --cc=linux-mm@kvack.org \
    --cc=mark@thundercompute.com \
    --cc=stable@vger.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