From: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: linux-kernel@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>,
Anders Roxell <anders.roxell@linaro.org>,
Arnd Bergmann <arnd@arndb.de>, Michal Hocko <mhocko@suse.com>,
linux-mm@kvack.org
Subject: Re: [PATCH] backing-dev: no need to check return value of debugfs_create functions
Date: Tue, 22 Jan 2019 17:07:59 +0100 [thread overview]
Message-ID: <20190122160759.mx3h7gjc23zmrvxc@linutronix.de> (raw)
In-Reply-To: <20190122152151.16139-8-gregkh@linuxfoundation.org>
On 2019-01-22 16:21:07 [+0100], Greg Kroah-Hartman wrote:
> diff --git a/mm/backing-dev.c b/mm/backing-dev.c
> index 8a8bb8796c6c..85ef344a9c67 100644
> --- a/mm/backing-dev.c
> +++ b/mm/backing-dev.c
> @@ -102,39 +102,25 @@ static int bdi_debug_stats_show(struct seq_file *m, void *v)
> }
> DEFINE_SHOW_ATTRIBUTE(bdi_debug_stats);
>
> -static int bdi_debug_register(struct backing_dev_info *bdi, const char *name)
> +static void bdi_debug_register(struct backing_dev_info *bdi, const char *name)
> {
> - if (!bdi_debug_root)
> - return -ENOMEM;
> -
> bdi->debug_dir = debugfs_create_dir(name, bdi_debug_root);
If this fails then ->debug_dir is NULL
> - if (!bdi->debug_dir)
> - return -ENOMEM;
> -
> - bdi->debug_stats = debugfs_create_file("stats", 0444, bdi->debug_dir,
> - bdi, &bdi_debug_stats_fops);
> - if (!bdi->debug_stats) {
> - debugfs_remove(bdi->debug_dir);
> - bdi->debug_dir = NULL;
> - return -ENOMEM;
> - }
>
> - return 0;
> + debugfs_create_file("stats", 0444, bdi->debug_dir, bdi,
> + &bdi_debug_stats_fops);
then this creates the stats file in the root folder and
> }
>
> static void bdi_debug_unregister(struct backing_dev_info *bdi)
> {
> - debugfs_remove(bdi->debug_stats);
> - debugfs_remove(bdi->debug_dir);
> + debugfs_remove_recursive(bdi->debug_dir);
this won't remove it.
If you return for "debug_dir == NULL" then it is a nice cleanup.
Sebastian
next prev parent reply other threads:[~2019-01-22 16:08 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-22 15:21 Greg Kroah-Hartman
2019-01-22 16:07 ` Sebastian Andrzej Siewior [this message]
2019-01-22 16:25 ` Greg Kroah-Hartman
2019-01-22 17:19 ` Sebastian Andrzej Siewior
2019-01-22 18:33 ` Greg Kroah-Hartman
2019-01-22 18:46 ` Qian Cai
2019-01-22 20:28 ` Sebastian Andrzej Siewior
2019-01-23 6:46 ` Greg Kroah-Hartman
2019-01-23 21:35 ` Sebastian Andrzej Siewior
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=20190122160759.mx3h7gjc23zmrvxc@linutronix.de \
--to=bigeasy@linutronix.de \
--cc=akpm@linux-foundation.org \
--cc=anders.roxell@linaro.org \
--cc=arnd@arndb.de \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@suse.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox