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>
Subject: Re: [PATCH] kprobes: no need to check return value of debugfs_create functions
Date: Wed, 23 Jan 2019 17:10:00 +0900 [thread overview]
Message-ID: <20190123171000.b1cbc9e1b52251bdd78b2338@kernel.org> (raw)
In-Reply-To: <20190123065422.GA27466@kroah.com>
On Wed, 23 Jan 2019 07:54:22 +0100
Greg Kroah-Hartman <gregkh@linuxfoundation.org> wrote:
> On Wed, Jan 23, 2019 at 11:15:16AM +0900, Masami Hiramatsu wrote:
> > 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...)
>
> dir == NULL means the system is out of memory. Which I'll change and
> just make it return an error, so it is fine to ignore this value.
Got it! Thanks!
Acked-by: Masami Hiramatsu <mhiramat@kernel.org>
>
> thanks,
>
> greg k-h
--
Masami Hiramatsu <mhiramat@kernel.org>
prev parent reply other threads:[~2019-01-23 8:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-22 15:21 Greg Kroah-Hartman
2019-01-23 2:15 ` Masami Hiramatsu
2019-01-23 6:54 ` Greg Kroah-Hartman
2019-01-23 8:10 ` Masami Hiramatsu [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=20190123171000.b1cbc9e1b52251bdd78b2338@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
Powered by JetHome