From: SJ Park <sj@kernel.org>
To: Harish CS <harish.cs.ss24@gmail.com>
Cc: SJ Park <sj@kernel.org>, damon@lists.linux.dev
Subject: Re: Regarding additional fixes for on node memcg quota metric issues
Date: Mon, 13 Jul 2026 07:57:51 -0700 [thread overview]
Message-ID: <20260713145752.40192-1-sj@kernel.org> (raw)
In-Reply-To: <CAGjpMsSMG2kaEWfP+fFw1PN13Adj_t81kzh-SDppnWQXRw88Yg@mail.gmail.com>
Hello Harish,
On Mon, 13 Jul 2026 12:32:17 +0530 Harish CS <harish.cs.ss24@gmail.com> wrote:
> Hello SJ,
>
> I came across the Sashiko review of damos_get_node_memcg_used_bp(), which
> identified possible unsigned underflow, division-by-zero, and 32-bit
> overflow issues in thenode_memcg_{used,free}_bp quota metric calculation.
> I saw your response that you planned to work on these findings separately.
> I am a newcomer to DAMON and upstream kernel development, and I am
> interested in contributing to this work. Are these issues still open,and
> would it be okay for me to work on them?
Yes, please feel free to work on it and send patches! :)
>
> And I would appreciate some initial direction on the approach on validating
> the fix.
I don't think it is easy to be tested. Many Sashiko-found bugs are
theoretically possible but not very common.
Maybe you could run DAMON selftests, kunit tests and/or even DAMON test suite
for correctness [1] and ensure your change doesn't regress at least existing
tests?
>
> Please let me know whether this would be a reasonable starting point or if
> you would recommend a different approach.
I think this is a reasonable starting point. Thank you for considering
contribution!
>
> Parent Bug Discussion:
> https://lore.kernel.org/20260329153425.47097-1-sj@kernel.org/
> Thank you for your time and guidance.
>
> Regards,
> Harish C S
>
[1] https://github.com/damonitor/damon-tests/tree/master/corr
Thanks,
SJ
parent reply other threads:[~2026-07-13 14:58 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <CAGjpMsSMG2kaEWfP+fFw1PN13Adj_t81kzh-SDppnWQXRw88Yg@mail.gmail.com>]
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=20260713145752.40192-1-sj@kernel.org \
--to=sj@kernel.org \
--cc=damon@lists.linux.dev \
--cc=harish.cs.ss24@gmail.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 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.