From: Bagas Sanjaya <bagasdotme@gmail.com>
To: SeongJae Park <sj@kernel.org>, akpm@linux-foundation.org
Cc: badari.pulavarty@intel.com, damon@lists.linux.dev,
linux-mm@kvack.org, linux-kernel@vger.kernel.org,
stable@vger.kernel.org
Subject: Re: [PATCH v2] mm/damon/dbgfs: avoid duplicate context directory creation
Date: Sat, 20 Aug 2022 09:29:24 +0700 [thread overview]
Message-ID: <69366c8b-9bbb-7d4c-4d0d-4948d04e71bb@gmail.com> (raw)
In-Reply-To: <20220819171930.16166-1-sj@kernel.org>
On 8/20/22 00:19, SeongJae Park wrote:
> From: Badari Pulavarty <badari.pulavarty@intel.com>
>
> When user tries to create a DAMON context via the DAMON debugfs
> interface with a name of an already existing context, the context
> directory creation silently fails but the context is added in the
> internal data structure. As a result, memory could leak and DAMON
> cannot be turned on. An example test case is as below:
>
> # cd /sys/kernel/debug/damon/
> # echo "off" > monitor_on
> # echo paddr > target_ids
> # echo "abc" > mk_context
> # echo "abc" > mk_context
> # echo $$ > abc/target_ids
> # echo "on" > monitor_on <<< fails
>
> This commit fixes the issue by checking if the name already exist and
> immediately returning '-EEXIST' in the case.
>
Meh...
SJ, I have seen most (if not all of) your patches uses descriptive mood
instead of imperative. Better say "Fix the issue by checking ...".
--
An old man doll... just what I always wanted! - Clara
prev parent reply other threads:[~2022-08-20 2:29 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-19 17:19 [PATCH v2] mm/damon/dbgfs: avoid duplicate context directory creation SeongJae Park
2022-08-19 21:08 ` Andrew Morton
2022-08-19 21:16 ` SeongJae Park
2022-08-19 22:44 ` Andrew Morton
2022-08-19 23:05 ` SeongJae Park
2022-08-20 17:32 ` Greg KH
2022-08-21 17:52 ` SeongJae Park
2022-08-20 2:29 ` Bagas Sanjaya [this message]
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=69366c8b-9bbb-7d4c-4d0d-4948d04e71bb@gmail.com \
--to=bagasdotme@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=badari.pulavarty@intel.com \
--cc=damon@lists.linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=sj@kernel.org \
--cc=stable@vger.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.