All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sasha Levin <sashal@kernel.org>
To: SJ Park <sj@kernel.org>
Cc: 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.12.y v2] mm/damon/core: error damos_commit_quota_goal() for zero target_value
Date: Mon, 26 Oct 2026 20:06:23 -0400	[thread overview]
Message-ID: <at_q_2pemJCnUvBZ@laps> (raw)
In-Reply-To: <20261027000120.156623-1-sj@kernel.org>

On Mon, Oct 26, 2026 at 05:01:20PM -0700, SJ Park wrote:
>Hello Sasha,
>
>On Mon, 26 Oct 2026 18:55:58 -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.12, thanks.
>
>I'm sorry but could you please unqueue?  Sashiko found [1] a bug that can leak
>pids.

No problem, now dropped.

>Also, could we avoid queueing DAMON patches that marked as RFC in general?

Sorry about this. We don't normally get RFC tags for backports so my brain
didn't register this at all :)

-- 
Thanks,
Sasha

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

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-26 13:55 [RFC PATCH 6.12.y v2] mm/damon/core: error damos_commit_quota_goal() for zero target_value SJ Park
2026-10-26 14:11 ` sashiko-bot
2026-10-26 15:08   ` SJ Park
2026-10-26 22:55 ` Sasha Levin
2026-10-27  0:01   ` SJ Park
2026-10-27  0:06     ` Sasha Levin [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=at_q_2pemJCnUvBZ@laps \
    --to=sashal@kernel.org \
    --cc=akpm@linux-foundation.org \
    --cc=damon@lists.linux.dev \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=sj@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 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.