From: "Prashant Bhole" <bhole_prashant_q7@lab.ntt.co.jp>
To: "'Jakub Kicinski'" <jakub.kicinski@netronome.com>
Cc: "'David Miller'" <davem@davemloft.net>, <netdev@vger.kernel.org>
Subject: RE: [PATCH net-next] netdevsim: correctly check return value of debugfs_create_dir
Date: Wed, 20 Dec 2017 09:38:52 +0900 [thread overview]
Message-ID: <024a01d3792a$e92c7ab0$bb857010$@lab.ntt.co.jp> (raw)
In-Reply-To: <20171219163014.1434bb62@cakuba.netronome.com>
> From: Jakub Kicinski [mailto:jakub.kicinski@netronome.com]
>
> On Wed, 20 Dec 2017 09:16:01 +0900, Prashant Bhole wrote:
> > > From: David Miller [mailto:davem@davemloft.net]
> > >
> > > 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.
> >
> > Right. I am planning to do following (quoting previous mail), In
> > debugfs error will not be ignored in modules load.
> > -----------
> > Dave,
> > Thanks for comments. I will try to fix error handling in netdevsim
first.
> >
> > Jakub,
> > Let's decide with an example. The typical directory structure for
> > netdevsim interface is as below:
> > /sys/kernel/debug/netdevsim/sim0/bpf_bound_progs/
> > Please let me know if you are ok with following:
> >
> > 1) If debugfs_create_dir() fails in module_init, let's keep it fatal
> > error with corrected condition:
> > + if (IS_ERR_OR_NULL(nsim_ddir))
> > + return -ENOMEM;
>
> Ack.
>
> > 2) In case sim0 or bpf_bound_progs are fail to create, we need to add
> > checks before creating any file in them.
>
> What do you mean by "check before"? Checking if creation of each file
fails or
> not, or something different?
For example:
I will check if state->ddir is not NULL before creating files in it.
if (state->ddir) {
debugfs_create_u32("id", 0400, state->ddir, &prog->aux->id);
debugfs_create_file("state", 0400, state->ddir,
&state->state, &nsim_bpf_string_fops);
debugfs_create_bool("loaded", 0400, state->ddir, &state->is_loaded);
}
-Prashant
next prev parent reply other threads:[~2017-12-20 0:40 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
2017-12-20 0:16 ` Prashant Bhole
2017-12-20 0:30 ` Jakub Kicinski
2017-12-20 0:38 ` Prashant Bhole [this message]
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='024a01d3792a$e92c7ab0$bb857010$@lab.ntt.co.jp' \
--to=bhole_prashant_q7@lab.ntt.co.jp \
--cc=davem@davemloft.net \
--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).