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: jakub.kicinski@netronome.com, netdev@vger.kernel.org
Subject: Re: [PATCH net-next] netdevsim: correctly check return value of debugfs_create_dir
Date: Tue, 19 Dec 2017 09:11:52 -0500 (EST)	[thread overview]
Message-ID: <20171219.091152.920867492172236638.davem@davemloft.net> (raw)
In-Reply-To: <014801d37884$3cc5d290$b65177b0$@lab.ntt.co.jp>

From: "Prashant Bhole" <bhole_prashant_q7@lab.ntt.co.jp>
Date: Tue, 19 Dec 2017 13:45:47 +0900

> I tried to evaluate whether fixing return value of debugfs_create_dir() (and
> friends) will be useful or not because it has not been changed since very
> long time. Now I am not much convinced about changing this api. 
> 
> Important and possible error codes could be -EEXIST and -ENOMEM. Suppose
> -EEXIST is returned, IMO the directory shouldn't exists in the first place
> because it is specific to particular module. Also, there is no point in
> creating file in such directory, because directory owner (creator) might
> remove it too. This means there are less chances that api change will be
> useful. Please let me know your opinion on it.
> 
> If you are ok with above explanation, shall I submit v2 for this patch?

Well, something is seriously wrong if the directory exists already.

It could be that two netdevsim modules, independantly compiled, are trying
to be loaded.

Wouldn't it clearly be desirable to fail and not load the module in
that case?

This is why I think ignoring debugfs errors is foolish.

  reply	other threads:[~2017-12-19 14:11 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
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 [this message]
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=20171219.091152.920867492172236638.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).