From: SJ Park <sj@kernel.org>
To: sashiko-bot@kernel.org
Cc: SJ Park <sj@kernel.org>, damon@lists.linux.dev
Subject: Re: [PATCH 3/6] selftests/damon: add script dir to sys.path for PYTHONSAFEPATH compatibility
Date: Mon, 14 Sep 2026 07:48:53 -0700 [thread overview]
Message-ID: <20260914144854.94549-1-sj@kernel.org> (raw)
In-Reply-To: <20260914143741.AAC251F000FF@smtp.kernel.org>
On Mon, 14 Sep 2026 14:37:41 +0000 sashiko-bot@kernel.org wrote:
> Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
> - [Medium] The patch incompletely fixes PYTHONSAFEPATH compatibility by omitting 3 out of 10 DAMON Python selftests, creating an inconsistent state and a commit message mismatch.
> --
>
> commit da82d013622fc33202048b811231e1ede806c92f
> Author: Eva Kurchatova <eva.kurchatova@virtuozzo.com>
>
> selftests/damon: add script dir to sys.path for PYTHONSAFEPATH compatibility
>
> This commit adds the script's directory to sys.path for seven DAMON Python
> selftests to ensure they can import the _damon_sysfs helper module when
> run under Python's safe path mode.
>
> > This breaks all 7 DAMON Python selftests that import the _damon_sysfs
> > helper module located in the same directory:
>
> [Severity: Medium]
> Are there additional DAMON Python selftests that also need this fix?
>
> The commit message states there are 7 tests, but it appears 3 additional
> tests in the same directory also import _damon_sysfs and were omitted
> from this patch.
>
> For example, in tools/testing/selftests/damon/sysfs.py:
> import _damon_sysfs
>
> And in tools/testing/selftests/damon/sysfs_refresh.py:
> import _damon_sysfs
>
> And in tools/testing/selftests/damon/sysfs_no_op_commit_break.py:
> import _damon_sysfs
>
> Will these scripts still fail with a ModuleNotFoundError when run in
> environments that enforce PYTHONSAFEPATH=1?
Agreed, but not necessarily a blocker of this patch. I will separately work on
the other tests.
>
> --
> Sashiko AI review · https://sashiko.dev/#/patchset/20260914141952.91465-1-sj@kernel.org?part=3
Thanks,
SJ
next prev parent reply other threads:[~2026-09-14 14:49 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-14 14:19 [PATCH 0/6] mm/damon: misc improvements in tests and documents SJ Park
2026-09-14 14:19 ` [PATCH 1/6] selftests/damon: stop kdamond on error exits of no-op commit test SJ Park
2026-09-14 14:30 ` sashiko-bot
2026-09-14 14:19 ` [PATCH 2/6] selftests/damon: ignore test-generated damon_dump_output SJ Park
2026-09-14 14:31 ` sashiko-bot
2026-09-14 14:19 ` [PATCH 3/6] selftests/damon: add script dir to sys.path for PYTHONSAFEPATH compatibility SJ Park
2026-09-14 14:37 ` sashiko-bot
2026-09-14 14:48 ` SJ Park [this message]
2026-09-14 14:19 ` [PATCH 4/6] mm/damon/tests/core-kunit: improve nr_samples_per_aggr test isolation SJ Park
2026-09-14 14:38 ` sashiko-bot
2026-09-14 14:19 ` [PATCH 5/6] Docs/mm/damon/design: clarify when qt_exceeds increases SJ Park
2026-09-14 14:39 ` sashiko-bot
2026-09-14 14:19 ` [PATCH 6/6] Docs/mm/damon/design: fix typos in temporal auto-tuning algorithm section SJ Park
2026-09-14 14:40 ` sashiko-bot
2026-09-14 14:50 ` [PATCH 0/6] mm/damon: misc improvements in tests and documents SJ Park
2026-09-15 2:00 ` 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=20260914144854.94549-1-sj@kernel.org \
--to=sj@kernel.org \
--cc=damon@lists.linux.dev \
--cc=sashiko-bot@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