From: SJ Park <sj@kernel.org>
To: SJ Park <sj@kernel.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
stable@vger.kernel.org,
Brendan Higgins <brendan.higgins@linux.dev>,
David Gow <davidgow@davidgow.net>,
Fernand Sieber <sieberf@amazon.com>,
Leonard Foerster <foersleo@amazon.de>,
Quanmin Yan <yanquanmin1@huawei.com>,
SeongJae Park <sjpark@amazon.de>,
Shakeel Butt <shakeel.butt@linux.dev>,
damon@lists.linux.dev, kunit-dev@googlegroups.com,
linux-kernel@vger.kernel.org, linux-kselftest@vger.kernel.org,
linux-mm@kvack.org
Subject: Re: [PATCH v1.1 0/6] mm/damon: unurgent fixes for infinite loop, NULL de-ref and races
Date: Tue, 14 Jul 2026 20:33:25 -0700 [thread overview]
Message-ID: <20260715033325.109466-1-sj@kernel.org> (raw)
In-Reply-To: <20260715031002.108504-1-sj@kernel.org>
On Tue, 14 Jul 2026 20:09:55 -0700 SJ Park <sj@kernel.org> wrote:
> Sashiko found a few issues in DAMON that could cause infinite loop, NULL
> dereference and monitoring results degradation. The first two sounds
> scary but the infinite loop happens only under unreasonable user setup.
> The NULL dereference is only in a unit test. Monitoring results
> degradation is trivial since it is only best-effort, and those happens
> from only unlikely races. Still those are bugs that better to fix if
> possible. Fix those.
Sashiko found no blocker for this series. Sashiko sent findings to damon@
mailing list [1], and I replied to all the comments. Please read those for
details.
[1] https://lore.kernel.org/damon/
Thanks,
SJ
[...]
next prev parent reply other threads:[~2026-07-15 3:33 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-15 3:09 [PATCH v1.1 0/6] mm/damon: unurgent fixes for infinite loop, NULL de-ref and races SJ Park
2026-07-15 3:09 ` [PATCH v1.1 1/6] mm/damon/core: avoid infinite kdamond_merge_regions() internal loop SJ Park
2026-07-15 3:09 ` [PATCH v1.1 2/6] mm/damon/tests/core-kunit: catch test failure in test_merge_regions_of() SJ Park
2026-07-15 3:09 ` [PATCH v1.1 3/6] mm/damon/vaddr: drop last same folio access check optimization SJ Park
2026-07-15 3:09 ` [PATCH v1.1 4/6] mm/damon/paddr: drop last same folio access check reuse optimization SJ Park
2026-07-15 3:10 ` [PATCH v1.1 5/6] mm/damon/sysfs: read addr_unit only once in damon_sysfs_apply_inputs() SJ Park
2026-07-15 3:10 ` [PATCH v1.1 6/6] mm/damon/sysfs: read ops_id " SJ Park
2026-07-15 3:33 ` SJ Park [this message]
2026-07-15 4:46 ` [PATCH v1.1 0/6] mm/damon: unurgent fixes for infinite loop, NULL de-ref and races Andrew Morton
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=20260715033325.109466-1-sj@kernel.org \
--to=sj@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=brendan.higgins@linux.dev \
--cc=damon@lists.linux.dev \
--cc=davidgow@davidgow.net \
--cc=foersleo@amazon.de \
--cc=kunit-dev@googlegroups.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=shakeel.butt@linux.dev \
--cc=sieberf@amazon.com \
--cc=sjpark@amazon.de \
--cc=stable@vger.kernel.org \
--cc=yanquanmin1@huawei.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