From: Greg KH <gregkh@linuxfoundation.org>
To: Raul Pazemecxas De Andrade <raul_pazemecxas@hotmail.com>
Cc: "sj@kernel.org" <sj@kernel.org>,
"security@kernel.org" <security@kernel.org>,
"damon@lists.linux.dev" <damon@lists.linux.dev>,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [BUG] mm/damon/core: dangling walk_control pointer in damos_walk() on inactive context
Date: Mon, 16 Feb 2026 16:52:38 +0100 [thread overview]
Message-ID: <2026021646-sandbox-duchess-5b7b@gregkh> (raw)
In-Reply-To: <CPUPR80MB8171025468965E583EF2490F956CA@CPUPR80MB8171.lamprd80.prod.outlook.com>
On Mon, Feb 16, 2026 at 03:34:44PM +0000, Raul Pazemecxas De Andrade wrote:
> Root cause
> ----------
>
> Commit bf0eaba0ff9c ("mm/damon/core: implement damos_walk()")
> introduced this function without cleanup on the -EINVAL error path.
>
> The sibling function damon_call() had the exact same bug and was
> fixed in f9132fbc2e83 by adding damon_call_handle_inactive_ctx()
> which removes the control object when the context is inactive.
> damos_walk() has no equivalent cleanup.
Can you submit a patch to resolve this to get credit for fixing the bug?
thanks,
greg k-h
next prev parent reply other threads:[~2026-02-16 15:52 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-16 15:34 Raul Pazemecxas De Andrade
2026-02-16 15:52 ` Greg KH [this message]
2026-02-16 16:18 ` [PATCH] " Raul Pazemecxas De Andrade
2026-02-16 16:26 ` Raul Pazemecxas De Andrade
2026-02-16 18:57 ` SeongJae Park
2026-02-16 21:47 ` SeongJae Park
2026-02-16 22:06 ` Raul Pazemecxas De Andrade
2026-02-16 16:26 ` [BUG] " Raul Pazemecxas De Andrade
-- strict thread matches above, loose matches on Subject: below --
2026-02-16 15:18 Raul Pazemecxas De Andrade
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=2026021646-sandbox-duchess-5b7b@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=damon@lists.linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=raul_pazemecxas@hotmail.com \
--cc=security@kernel.org \
--cc=sj@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