netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: bhole_prashant_q7@lab.ntt.co.jp
Cc: netdev@vger.kernel.org, jakub.kicinski@netronome.com
Subject: Re: [PATCH net-next] netdevsim: correctly check return value of debugfs_create_dir
Date: Fri, 08 Dec 2017 10:31:10 -0500 (EST)	[thread overview]
Message-ID: <20171208.103110.1740849637875852344.davem@davemloft.net> (raw)
In-Reply-To: <20171208005250.2972-1-bhole_prashant_q7@lab.ntt.co.jp>

From: Prashant Bhole <bhole_prashant_q7@lab.ntt.co.jp>
Date: Fri,  8 Dec 2017 09:52:50 +0900

> Return value is now checked with IS_ERROR_OR_NULL because
> debugfs_create_dir doesn't return error value. It either returns
> NULL or a valid pointer.
> 
> Signed-off-by: Prashant Bhole <bhole_prashant_q7@lab.ntt.co.jp>
> ---
>  drivers/net/netdevsim/netdev.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/drivers/net/netdevsim/netdev.c b/drivers/net/netdevsim/netdev.c
> index eb8c679fca9f..88d8ee2c89da 100644
> --- a/drivers/net/netdevsim/netdev.c
> +++ b/drivers/net/netdevsim/netdev.c
> @@ -469,7 +469,7 @@ static int __init nsim_module_init(void)
>  	int err;
>  
>  	nsim_ddir = debugfs_create_dir(DRV_NAME, NULL);
> -	if (IS_ERR(nsim_ddir))
> +	if (IS_ERR_OR_NULL(nsim_ddir))
>  		return PTR_ERR(nsim_ddir);

debugfs_create_dir() should really be fixed, either it uses error pointers
consistently and therefore always provides a suitable error code to return
or it always uses NULL.

This in-between behavior makes using it as an interface painful because
no clear meaning is given to NULL.

So please do the work necessary to make debugfs_create_dir()'s return
semantics clearer and more useful.

Thank you.

  parent reply	other threads:[~2017-12-08 15:31 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-08  0:52 [PATCH net-next] netdevsim: correctly check return value of debugfs_create_dir Prashant Bhole
2017-12-08  1:12 ` Jakub Kicinski
2017-12-08  2:12   ` Prashant Bhole
2017-12-08 15:31 ` David Miller [this message]
2017-12-11  4:46   ` Prashant Bhole
2017-12-11 18:40     ` Jakub Kicinski
2017-12-19  4:45       ` Prashant Bhole
2017-12-19 14:11         ` David Miller
2017-12-20  0:16           ` Prashant Bhole
2017-12-20  0:30             ` Jakub Kicinski
2017-12-20  0:38               ` Prashant Bhole
2017-12-20  0:45                 ` Jakub Kicinski
2017-12-20  0:54                   ` Prashant Bhole
2017-12-20  1:18                     ` Jakub Kicinski
2017-12-20  1:40                       ` Prashant Bhole

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=20171208.103110.1740849637875852344.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=bhole_prashant_q7@lab.ntt.co.jp \
    --cc=jakub.kicinski@netronome.com \
    --cc=netdev@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;
as well as URLs for NNTP newsgroup(s).