From: SeongJae Park <sj@kernel.org>
To: sashiko-bot@kernel.org
Cc: SeongJae Park <sj@kernel.org>, damon@lists.linux.dev
Subject: Re: [RFC PATCH v1.1 02/11] Docs/ABI/damon: document probe files
Date: Wed, 24 Jun 2026 22:25:19 -0700 [thread overview]
Message-ID: <20260625052520.92614-1-sj@kernel.org> (raw)
In-Reply-To: <20260625051413.972291F000E9@smtp.kernel.org>
On Thu, 25 Jun 2026 05:14:13 +0000 sashiko-bot@kernel.org wrote:
> Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
> - [Medium] Incorrect sysfs value 'memmcg' and typographical errors in DAMON probe ABI documentation.
> --
>
> commit 0777dacf66fdc3cce9315b7348cc989aa1d048f8
> Author: SeongJae Park <sj@kernel.org>
>
> Docs/ABI/damon: document probe files
>
> This commit updates the DAMON ABI documentation to include the new DAMON
> probe sysfs files, defining directories for probes, filters, and attributes.
>
> > diff --git a/Documentation/ABI/testing/sysfs-kernel-mm-damon b/Documentation/ABI/testing/sysfs-kernel-mm-damon
> > index b73e6bc28ea5f..2815f6bc05c18 100644
> > --- a/Documentation/ABI/testing/sysfs-kernel-mm-damon
> > +++ b/Documentation/ABI/testing/sysfs-kernel-mm-damon
> [ ... ]
> > +What: /sys/kernel/mm/damon/admin/kdamonds/<K>/contexts/<C>/monitoring_attrs/probes/<P>/filters/<F>/path
> > +Date: May 2026
> > +Contact: SeongJae Park <sj@kernel.org>
> > +Description: If 'memmcg' is written to the 'type' file, writing to and
> > + reading from this file sets and geets the path to the memory
> > + cgroup of the interest.
>
> [Severity: Medium]
> Is the expected type value documented correctly here? The documentation
> instructs users to write 'memmcg' to the type file, but the underlying kernel
> code strictly expects 'memcg'. If userspace follows this documentation, will
> the kernel reject the input with an -EINVAL error?
>
> Also, this isn't a bug, but there is a typo in this sentence where "geets"
> is written instead of "gets".
Good catches. Those are typos. Somehow nowadays my computer shows lags at
multiple things including BT keyboard input catch...
I will fix these in the next revision.
Thanks,
SJ
[...]
next prev parent reply other threads:[~2026-06-25 5:25 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-25 5:07 [RFC PATCH v1.1 00/11] mm/damon: update, optimize, and clean up doc, tests, and code SeongJae Park
2026-06-25 5:07 ` [RFC PATCH v1.1 01/11] Docs/mm/damon/design: update for DAMOS_QUOTA_NODE_ELIGIBLE_MEM_BP SeongJae Park
2026-06-25 5:13 ` sashiko-bot
2026-06-25 5:20 ` SeongJae Park
2026-06-25 5:07 ` [RFC PATCH v1.1 02/11] Docs/ABI/damon: document probe files SeongJae Park
2026-06-25 5:14 ` sashiko-bot
2026-06-25 5:25 ` SeongJae Park [this message]
2026-06-25 5:07 ` [RFC PATCH v1.1 03/11] mm/damon/tests/core-kunit: test damon_rand() SeongJae Park
2026-06-25 5:13 ` sashiko-bot
2026-06-25 5:37 ` SeongJae Park
2026-06-25 5:07 ` [RFC PATCH v1.1 04/11] selftests/damon/sysfs.sh: test multiple probe dirs creation SeongJae Park
2026-06-25 5:07 ` [RFC PATCH v1.1 05/11] selftests/damon/sysfs.sh: test {core,ops}_filters/ directories SeongJae Park
2026-06-25 5:07 ` [RFC PATCH v1.1 06/11] selftests/damon/sysfs.sh: test dests dir SeongJae Park
2026-06-25 5:14 ` sashiko-bot
2026-06-25 5:42 ` SeongJae Park
2026-06-25 5:07 ` [RFC PATCH v1.1 07/11] selftests/damon/sysfs.sh: test all files in quota goal dir SeongJae Park
2026-06-25 5:07 ` [RFC PATCH v1.1 08/11] mm/damon/core: reduce range setup in damon_commit_target_regions() SeongJae Park
2026-06-25 5:07 ` [RFC PATCH v1.1 09/11] mm/damon/sysfs: split probe setup function out SeongJae Park
2026-06-25 5:07 ` [RFC PATCH v1.1 10/11] mm/damon/sysfs: split out filters setup function SeongJae Park
2026-06-25 5:07 ` [RFC PATCH v1.1 11/11] mm/damon/sysfs: fix typos in probe_{add,rm}_dirs: s/attr/probe/ SeongJae 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=20260625052520.92614-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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.