All of 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>,
	stable@vger.kernel.org, damon@lists.linux.dev,
	Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH 6.18.y] mm/damon/core: avoid infinite kdamond_merge_regions() internal loop
Date: Fri, 11 Sep 2026 06:50:02 -0700	[thread overview]
Message-ID: <20260911135003.96395-1-sj@kernel.org> (raw)
In-Reply-To: <daily-reply-0037-re-damon-merge-regions-6-18@kernel.org>

On Fri, 11 Sep 2026 07:20:56 -0400 Sasha Levin <sashal@kernel.org> wrote:

> > Sashiko found a few issues in DAMON that could cause infinite loop,
> > NULL dereference and monitoring results degradation.
> 
> Holding this on all five branches for now. 6.18.y is newer than 6.12.y, 6.6.y,
> 6.1.y, and 5.15.y, and it needs a fix here first, but the patch you sent for
> 6.18.y does not apply: 6.18.y has since grown a count_age parameter
> through the same lines this patch touches.
> 
> Could you send an updated 6.18.y version rebased against the current count_age
> code?

Sure!  I just sent [1] it.

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

> Once that lands, the other four branches are ready to go.

Cool, let me know if there is anything that I can help!


Thanks,
SJ

[...]

      reply	other threads:[~2026-09-11 13:50 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <2026090831-drinkable-maybe-5e01@gregkh>
2026-09-09  4:15 ` [PATCH 6.18.y] mm/damon/core: avoid infinite kdamond_merge_regions() internal loop SJ Park
2026-09-09  4:25   ` sashiko-bot
2026-09-09 13:03   ` Greg KH
2026-09-10  0:37     ` SJ Park
2026-09-11 11:20   ` Sasha Levin
2026-09-11 13:50     ` 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=20260911135003.96395-1-sj@kernel.org \
    --to=sj@kernel.org \
    --cc=akpm@linux-foundation.org \
    --cc=damon@lists.linux.dev \
    --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 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.