From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Mark Bloch <markb@mellanox.com>
Cc: Leon Romanovsky <leon@kernel.org>,
Doug Ledford <dledford@redhat.com>,
Jason Gunthorpe <jgg@ziepe.ca>,
"linux-rdma@vger.kernel.org" <linux-rdma@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] IB: mlx5: no need to check return value of debugfs_create functions
Date: Tue, 5 Nov 2019 08:24:25 +0100 [thread overview]
Message-ID: <20191105072425.GD2587462@kroah.com> (raw)
In-Reply-To: <50a30aa3-3924-4fd1-f644-2fd2b184ec0e@mellanox.com>
On Tue, Nov 05, 2019 at 12:48:16AM +0000, Mark Bloch wrote:
>
>
> On 11/3/19 11:41 PM, Greg Kroah-Hartman 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: Leon Romanovsky <leon@kernel.org>
> > Cc: Doug Ledford <dledford@redhat.com>
> > Cc: Jason Gunthorpe <jgg@ziepe.ca>
> > Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
> > ---
> > drivers/infiniband/hw/mlx5/main.c | 62 +++++++---------------------
> > drivers/infiniband/hw/mlx5/mlx5_ib.h | 9 +---
> > 2 files changed, 16 insertions(+), 55 deletions(-)
> >
> > Note, I kind of need to take this through my tree now as I broke the
> > build due to me changing the use of debugfs_create_atomic_t() in my
> > tree and not noticing this being used here. Sorry about that, any
> > objections?
> >
> > And 0-day seems really broken to have missed this for the past months,
> > ugh, I need to stop relying on it...
> >
> >
> > diff --git a/drivers/infiniband/hw/mlx5/main.c b/drivers/infiniband/hw/mlx5/main.c
> > index 831539419c30..059db0610445 100644
> > --- a/drivers/infiniband/hw/mlx5/main.c
> > +++ b/drivers/infiniband/hw/mlx5/main.c
> > @@ -5710,11 +5710,10 @@ static int mlx5_ib_rn_get_params(struct ib_device *device, u8 port_num,
> >
> > static void delay_drop_debugfs_cleanup(struct mlx5_ib_dev *dev)
> > {
> > - if (!dev->delay_drop.dbg)
> > + if (!dev->delay_drop.dir_debugfs)
>
> Shouldn't this be:
> if (IS_ERR(dev->delay_drop.dir_debugfs))
> return;
> ?
No, really there should not be any check at all as there is no problem
taking the result of a debugfs call and feeding it back into another
call. There is no need to check these return values at all.
So the code should just be dropped, I can do that as a follow-on if you
want me to.
> > return;
> > - debugfs_remove_recursive(dev->delay_drop.dbg->dir_debugfs);
> > - kfree(dev->delay_drop.dbg);
> > - dev->delay_drop.dbg = NULL;
> > + debugfs_remove_recursive(dev->delay_drop.dir_debugfs);
> > + dev->delay_drop.dir_debugfs = NULL;
>
> Thinking about this more, we already do something like this:
> if (IS_ERR_OR_NULL(dentry))
> return;
> inside debugfs_remove_recursive(), so this entire function can be reduced
> to just calling debugfs_remove_recursive().
Very true, I was trying to keep the patch simple :)
thanks,
greg k-h
next prev parent reply other threads:[~2019-11-05 7:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-04 7:41 [PATCH] IB: mlx5: no need to check return value of debugfs_create functions Greg Kroah-Hartman
2019-11-04 20:59 ` Jason Gunthorpe
2019-11-04 21:08 ` Greg Kroah-Hartman
2019-11-05 0:48 ` Mark Bloch
2019-11-05 7:24 ` Greg Kroah-Hartman [this message]
2019-11-05 14:30 ` Leon Romanovsky
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=20191105072425.GD2587462@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=dledford@redhat.com \
--cc=jgg@ziepe.ca \
--cc=leon@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=markb@mellanox.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