linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: SeongJae Park <sj@kernel.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: Fri, 19 Aug 2022 14:08:09 -0700	[thread overview]
Message-ID: <20220819140809.1e3929fd8f50bfc32cae31d3@linux-foundation.org> (raw)
In-Reply-To: <20220819171930.16166-1-sj@kernel.org>

On Fri, 19 Aug 2022 17:19:30 +0000 SeongJae Park <sj@kernel.org> 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.
> 
> ...
>
> --- a/mm/damon/dbgfs.c
> +++ b/mm/damon/dbgfs.c
> @@ -795,7 +795,7 @@ static void dbgfs_destroy_ctx(struct damon_ctx *ctx)
>   */
>  static int dbgfs_mk_context(char *name)
>  {
> -	struct dentry *root, **new_dirs, *new_dir;
> +	struct dentry *root, **new_dirs, *new_dir, *dir;
>  	struct damon_ctx **new_ctxs, *new_ctx;
>  
>  	if (damon_nr_running_ctxs())
> @@ -817,6 +817,12 @@ static int dbgfs_mk_context(char *name)
>  	if (!root)
>  		return -ENOENT;
>  
> +	dir = debugfs_lookup(name, root);
> +	if (dir) {
> +		dput(dir);
> +		return -EEXIST;
> +	}
> +
>  	new_dir = debugfs_create_dir(name, root);
>  	dbgfs_dirs[dbgfs_nr_ctxs] = new_dir;

It would be simpler (and less racy) to check the debugfs_create_dir()
return value for IS_ERR()?



  reply	other threads:[~2022-08-19 21:08 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-19 17:19 SeongJae Park
2022-08-19 21:08 ` Andrew Morton [this message]
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

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=20220819140809.1e3929fd8f50bfc32cae31d3@linux-foundation.org \
    --to=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox