linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: SeongJae Park <sj@kernel.org>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: SeongJae Park <sj@kernel.org>,
	"# 6 . 17-rc1" <stable@vger.kernel.org>,
	damon@lists.linux.dev, kernel-team@meta.com,
	linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: [PATCH 0/3] samples/damon: fix boot time enable handling fixup merge mistakes
Date: Mon,  8 Sep 2025 20:51:41 -0700	[thread overview]
Message-ID: <20250909035141.7545-1-sj@kernel.org> (raw)
In-Reply-To: <20250908193548.a153ef39d85cc54816950f71@linux-foundation.org>

On Mon, 8 Sep 2025 19:35:48 -0700 Andrew Morton <akpm@linux-foundation.org> wrote:

> On Mon,  8 Sep 2025 19:22:35 -0700 SeongJae Park <sj@kernel.org> wrote:
> 
> > First three patches of the patch series "mm/damon: fix misc bugs in
> > DAMON modules" [1] was trying to fix boot time DAMON sample modules
> > enabling issues by avoiding starting DAMON before the module
> > initialization phase.  However, probably by a mistake during a merge,
> > only half of the change is merged, and the part for avoiding the
> > starting of DAMON before the module initialized is missed.  So the
> > problem is not solved.  Fix those.
> > 
> > Note that the broken commits are merged into 6.17-rc1, but also
> > backported to relevant stable kernels.  So this series also need to be
> > merged into the stable kernels.  Hence Cc-ing stable@.
> 
> That's unfortunate, but the about doesn't actually tell us what this
> series does.  

Good point.  The issue is that the sample modules can crash if those are
enabled at boot time before DAMON is initialized, via kernel command line.

Would you prefer me sending another version of this patch series with an
elaborated cover letter?

> 
> > [1] https://lore.kernel.org/20250706193207.39810-1-sj@kernel.org
> 
> Presumably it's in there somewhere?

You're right.  Both the cover letter and the individual fix patches (first
three of the series) describes the issue and origin broken commit.

Please let me know if there is anything I can help for this patch series from
my side :)


Thanks,
SJ


  reply	other threads:[~2025-09-09  3:51 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-09  2:22 SeongJae Park
2025-09-09  2:22 ` [PATCH 1/3] samples/damon/wsse: avoid starting DAMON before initialization SeongJae Park
2025-09-09  2:22 ` [PATCH 2/3] samples/damon/prcl: " SeongJae Park
2025-09-09  2:22 ` [PATCH 3/3] samples/damon/mtier: " SeongJae Park
2025-09-09  2:35 ` [PATCH 0/3] samples/damon: fix boot time enable handling fixup merge mistakes Andrew Morton
2025-09-09  3:51   ` SeongJae Park [this message]
2025-09-09  4:18     ` Andrew Morton
2025-09-09  4:30       ` SeongJae Park

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=20250909035141.7545-1-sj@kernel.org \
    --to=sj@kernel.org \
    --cc=akpm@linux-foundation.org \
    --cc=damon@lists.linux.dev \
    --cc=kernel-team@meta.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.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