public inbox for stable@vger.kernel.org
 help / color / mirror / Atom feed
From: SeongJae Park <sj@kernel.org>
To: gregkh@linuxfoundation.org
Cc: SeongJae Park <sj@kernel.org>,
	akpm@linux-foundation.org, stable@vger.kernel.org
Subject: Re: FAILED: patch "[PATCH] mm/damon/core: fix damos_walk() vs kdamond_fn() exit race" failed to apply to 6.18-stable tree
Date: Fri,  1 May 2026 20:06:23 -0700	[thread overview]
Message-ID: <20260502030624.127487-1-sj@kernel.org> (raw)
In-Reply-To: <2026050141-likewise-trapeze-f1cc@gregkh>

On Fri, 01 May 2026 13:01:41 +0200 <gregkh@linuxfoundation.org> wrote:

> 
> The patch below does not apply to the 6.18-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-6.18.y
> git checkout FETCH_HEAD
> git cherry-pick -x 33c3f6c2b48cd84b441dba1ee3e62290e53930f4
> # <resolve conflicts, build, test, etc.>
> git commit -s
> git send-email --to '<stable@vger.kernel.org>' --in-reply-to '2026050141-likewise-trapeze-f1cc@gregkh' --subject-prefix 'PATCH 6.18.y' HEAD^..
> 
> Possible dependencies:
> 
> 
> 
> thanks,
> 
> greg k-h
> 
> ------------------ original commit in Linus's tree ------------------
> 
> >From 33c3f6c2b48cd84b441dba1ee3e62290e53930f4 Mon Sep 17 00:00:00 2001
> From: SeongJae Park <sj@kernel.org>
> Date: Fri, 27 Mar 2026 16:33:15 -0700
> Subject: [PATCH] mm/damon/core: fix damos_walk() vs kdamond_fn() exit race

The patch should be merged together with daf51c2e9585 ("mm/damon/core: fix
damon_call() vs kdamond_fn() exit race") but seems you tried to apply the patch
without the dependent one.  Nonetheless, the previous one also cannot be
cleanly applied.  Even after the previous one is applied, the patch cannot
cleanly applied, either.  So I posted the two patches [1,2] that ported for
6.18, as replies to this original mail.

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


Thanks,
SJ
 
[...]

      parent reply	other threads:[~2026-05-02  3:06 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-01 11:01 FAILED: patch "[PATCH] mm/damon/core: fix damos_walk() vs kdamond_fn() exit race" failed to apply to 6.18-stable tree gregkh
2026-05-02  3:02 ` [PATCH 1/2] mm/damon/core: fix damon_call() vs kdamond_fn() exit race SeongJae Park
2026-05-02  3:02   ` [PATCH 2/2] mm/damon/core: fix damos_walk() " SeongJae Park
2026-05-02  3:06 ` SeongJae 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=20260502030624.127487-1-sj@kernel.org \
    --to=sj@kernel.org \
    --cc=akpm@linux-foundation.org \
    --cc=gregkh@linuxfoundation.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