From: Masami Hiramatsu <mhiramat@kernel.org>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: linux-kernel@vger.kernel.org,
"Naveen N. Rao" <naveen.n.rao@linux.ibm.com>,
Anil S Keshavamurthy <anil.s.keshavamurthy@intel.com>,
"David S. Miller" <davem@davemloft.net>,
Masami Hiramatsu <mhiramat@kernel.org>
Subject: Re: [PATCH] kprobes: no need to check return value of debugfs_create functions
Date: Wed, 23 Jan 2019 11:15:16 +0900 [thread overview]
Message-ID: <20190123111516.d5fd81cb315810235205fbeb@kernel.org> (raw)
In-Reply-To: <20190122152151.16139-47-gregkh@linuxfoundation.org>
On Tue, 22 Jan 2019 16:21:46 +0100
Greg Kroah-Hartman <gregkh@linuxfoundation.org> wrote:
> When calling debugfs functions, there is no need to ever check the
> return value. The function can work or not, but the code logic should
> never do something different based on this.
>
> Cc: "Naveen N. Rao" <naveen.n.rao@linux.ibm.com>
> Cc: Anil S Keshavamurthy <anil.s.keshavamurthy@intel.com>
> Cc: "David S. Miller" <davem@davemloft.net>
> Cc: Masami Hiramatsu <mhiramat@kernel.org>
> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
> ---
> kernel/kprobes.c | 25 ++++++-------------------
> 1 file changed, 6 insertions(+), 19 deletions(-)
>
> diff --git a/kernel/kprobes.c b/kernel/kprobes.c
> index f4ddfdd2d07e..7287e7de2350 100644
> --- a/kernel/kprobes.c
> +++ b/kernel/kprobes.c
> @@ -2566,33 +2566,20 @@ static const struct file_operations fops_kp = {
>
> static int __init debugfs_kprobe_init(void)
> {
> - struct dentry *dir, *file;
> + struct dentry *dir;
> unsigned int value = 1;
>
> dir = debugfs_create_dir("kprobes", NULL);
> - if (!dir)
> - return -ENOMEM;
Here, I think IS_ERR(dir) is OK for debugfs_create_file(),
but dir == NULL has different meaning. I think we'd better
keep this check. (I see, -ENOMEM will be no good...)
Thank you,
>
> - file = debugfs_create_file("list", 0400, dir, NULL,
> - &debugfs_kprobes_operations);
> - if (!file)
> - goto error;
> + debugfs_create_file("list", 0400, dir, NULL,
> + &debugfs_kprobes_operations);
>
> - file = debugfs_create_file("enabled", 0600, dir,
> - &value, &fops_kp);
> - if (!file)
> - goto error;
> + debugfs_create_file("enabled", 0600, dir, &value, &fops_kp);
>
> - file = debugfs_create_file("blacklist", 0400, dir, NULL,
> - &debugfs_kprobe_blacklist_ops);
> - if (!file)
> - goto error;
> + debugfs_create_file("blacklist", 0400, dir, NULL,
> + &debugfs_kprobe_blacklist_ops);
>
> return 0;
> -
> -error:
> - debugfs_remove(dir);
> - return -ENOMEM;
> }
>
> late_initcall(debugfs_kprobe_init);
> --
> 2.20.1
>
--
Masami Hiramatsu <mhiramat@kernel.org>
next prev parent reply other threads:[~2019-01-23 2:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-22 15:21 [PATCH] kprobes: no need to check return value of debugfs_create functions Greg Kroah-Hartman
2019-01-23 2:15 ` Masami Hiramatsu [this message]
2019-01-23 6:54 ` Greg Kroah-Hartman
2019-01-23 8:10 ` Masami Hiramatsu
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=20190123111516.d5fd81cb315810235205fbeb@kernel.org \
--to=mhiramat@kernel.org \
--cc=anil.s.keshavamurthy@intel.com \
--cc=davem@davemloft.net \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=naveen.n.rao@linux.ibm.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