Linux kernel -stable discussions
 help / color / mirror / Atom feed
From: SJ Park <sj@kernel.org>
To: stable@vger.kernel.org,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Sasha Levin <sashal@kernel.org>
Cc: SJ Park <sj@kernel.org>,
	damon@lists.linux.dev, Andrew Morton <akpm@linux-foundation.org>
Subject: [stable] Wrongly applied DAMON patches
Date: Sat,  7 Nov 2026 13:01:22 -0800	[thread overview]
Message-ID: <20261107210123.270641-1-sj@kernel.org> (raw)

Hello stable@ maintainers,


A few DAMON patches unintentionally got [1] Cc:stable@ tags and queued for a
few stable kernels.  Some of those even causing test failures.  Below are my
best-effort (having no Fixes: tag) search of the unintentionally queued patches
on stable-rc tree.  Could you please unqueue those?  If you prefer keeping
patches that not intended to be queued for stable@ but not found to cause test
failures, that's also fine for me.

7.3.y
=====

b7156fe3b9cdb mm/damon/tests/core-kunit: test the size charged for a filter-trimmed region
2ae8e0a3f49e3 mm/damon/core-kunit: test invalid damos filter commits
96af19427e2bf mm/damon/core-kunit: extend damos_commit_filter_for() for wrong input
f13b460f99105 mm/damon/core: return an error from damos_commit_filter_arg()

The third commit is causing a test failure.

6.18.y
======

c088f850b5e60 mm/damon/tests/core-kunit: test the size charged for a filter-trimmed region

The commit is also causing a test failure.

6.12.y
======

fc18efc64dc84 mm/damon/tests/core-kunit: test the size charged for a filter-trimmed region

The commit is also causing a test failure.

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


Thanks,
SJ

                 reply	other threads:[~2026-11-07 21:01 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20261107210123.270641-1-sj@kernel.org \
    --to=sj@kernel.org \
    --cc=akpm@linux-foundation.org \
    --cc=damon@lists.linux.dev \
    --cc=gregkh@linuxfoundation.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