Linux-mm Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: SJ Park <sj@kernel.org>
To: Sasha Levin <sashal@kernel.org>
Cc: SJ Park <sj@kernel.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	damon@lists.linux.dev, linux-kernel@vger.kernel.org,
	linux-mm@kvack.org, stable@vger.kernel.org
Subject: Re: [RFC PATCH 6.18.y v2] mm/damon/core: error damos_commit_quota_goal() for zero target_value
Date: Mon, 26 Oct 2026 17:04:38 -0700	[thread overview]
Message-ID: <20261027000439.156775-1-sj@kernel.org> (raw)
In-Reply-To: <2026-10-26-1-daily-reply-0006-damon-zero-target-value-6-18@kernel.org>

Hello Sasha,

On Mon, 26 Oct 2026 18:55:57 -0400 Sasha Levin <sashal@kernel.org> wrote:

> > Also, the upstream commit on this stable kernel can fix the issue for
> > parameters commit paths but DAMON start path.  That's because DAMON
> > start path does not invoke damon_commit_quota_goals().  To fix the path
> > with minimum change, add a new small validation of quota goal target
> > value before damon_start() call.
> 
> Queued for 6.18, thanks.

Thank you!  This and the porting for 7.2 [1] are ready to be queeud in my
opinion, though they have RFC tags, so no further action is needed.

That said, I add RFC tag to patches expecting those wouldn't be queued.  Could
we avoid queueing RFC DAMON patches to stable kernels from the next time?

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


Thanks,
SJ

[...]


      reply	other threads:[~2026-10-27  0:04 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-26 13:47 [RFC PATCH 6.18.y v2] mm/damon/core: error damos_commit_quota_goal() for zero target_value SJ Park
2026-10-26 22:55 ` Sasha Levin
2026-10-27  0:04   ` 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=20261027000439.156775-1-sj@kernel.org \
    --to=sj@kernel.org \
    --cc=akpm@linux-foundation.org \
    --cc=damon@lists.linux.dev \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=sashal@kernel.org \
    --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