Linux kernel -stable discussions
 help / color / mirror / Atom feed
From: SJ Park <sj@kernel.org>
To: Sasha Levin <sashal@kernel.org>
Cc: SJ Park <sj@kernel.org>,
	akpm@linux-foundation.org, brendan.higgins@linux.dev,
	davidgow@davidgow.net, usamaarif642@gmail.com,
	stable@vger.kernel.org
Subject: Re: FAILED: patch "[PATCH] mm/damon/core: disallow max < min damos filter range arguments commit" failed to apply to 7.3-stable tree
Date: Sat,  7 Nov 2026 09:36:36 -0800	[thread overview]
Message-ID: <20261107173637.109352-1-sj@kernel.org> (raw)
In-Reply-To: <20261107050426-failed-7.3-1bfb9384ae0e@kernel.org>

On Sat,  7 Nov 2026 05:04:27 -0500 Sasha Levin <sashal@kernel.org> wrote:

> The patch below does not apply to the 7.3-stable tree.
> If someone wants it applied there, or to any other stable or longterm
> tree, then please email the backport, including the original git commit
> id to <stable@vger.kernel.org>.
> 
> To reproduce the conflict and resubmit, you may use the following commands:
> 
> git fetch https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/ linux-7.3.y
> git checkout FETCH_HEAD
> git cherry-pick -x 1bfb9384ae0ed52d61eb601b655014b7815ff849
> # <resolve conflicts, build, test, etc.>
> git commit -s
> git send-email --to '<stable@vger.kernel.org>' --in-reply-to '20261107050426-failed-7.3-1bfb9384ae0e@kernel.org' --subject-prefix 'PATCH 7.3.y' 'HEAD^..'
> 
> Thanks,
> Sasha
> 
> ------------------ original commit in Linus's tree ------------------
> 
> >From 1bfb9384ae0ed52d61eb601b655014b7815ff849 Mon Sep 17 00:00:00 2001
> From: SJ Park <sj@kernel.org>
> Date: Mon, 14 Sep 2026 07:23:21 -0700
> Subject: [PATCH] mm/damon/core: disallow max < min damos filter range
>  arguments commit
> 
> damos_commit_filter_arg() receives range arguments for a few types of
> DAMOS filters.  It allows any range including max < min range.  It is fine
> for the logic, but makes no sense to support it.  Actually DAMON sysfs
> interface is doing the validation on its own.  To avoid duplicated
> validations in multiple DAMON API callers, it would be better to do the
> validation in the core layer.  Add a validation of the given range.
> 
> Link: https://lore.kernel.org/20260914142327.92510-5-sj@kernel.org
> Signed-off-by: SJ Park <sj@kernel.org>
> Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
> Cc: Brendan Higgins <brendan.higgins@linux.dev>
> Cc: David Gow <davidgow@davidgow.net>
> Cc: Usama Arif <usamaarif642@gmail.com>
> Cc: <stable@vger.kernel.org>

Including this, five DAMON patch cherry-pick failures [1,2,3,4] for 7.3.y are
reported last night

The patchex except the last one [4] don't Cc: stable@ and look like not
essential hotfixes.

Those are refactoring [1,2] or a very minor fix [3] that doesn't really impact
users.  Those are not built in porting-friendly way because those were not
meant to be hotfixes.  To port those, no small amount of refactoring or porting
of more dependencies are expected.

I don't mind porting non-Cc: stable@ DAMON patches to stable kernels.  And I'm
happy to help doing that.  But I'm not quite sure if this is indeed what you
want, or picked by a mistake.  Could you please confirm?

[1] https://lore.kernel.org/20261107050429-failed-7.3-1d2397b2c414@kernel.org
[2] https://lore.kernel.org/20261107050431-failed-7.3-cec08aad3def@kernel.org
[3] https://lore.kernel.org/20261107050434-failed-7.3-af19aff38d6f@kernel.org
[4] https://lore.kernel.org/20261107050537-failed-7.3-5695abc4e742@kernel.org


Thanks,
SJ

[...]

  reply	other threads:[~2026-11-07 17:36 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-07 10:04 FAILED: patch "[PATCH] mm/damon/core: disallow max < min damos filter range arguments commit" failed to apply to 7.3-stable tree Sasha Levin
2026-11-07 17:36 ` SJ Park [this message]
2026-11-07 19:43   ` SJ Park
2026-11-07 20:45     ` SJ 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=20261107173637.109352-1-sj@kernel.org \
    --to=sj@kernel.org \
    --cc=akpm@linux-foundation.org \
    --cc=brendan.higgins@linux.dev \
    --cc=davidgow@davidgow.net \
    --cc=sashal@kernel.org \
    --cc=stable@vger.kernel.org \
    --cc=usamaarif642@gmail.com \
    /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