From: Dan Carpenter <dan.carpenter@oracle.com>
To: walter harms <wharms@bfs.de>
Cc: kernel-janitors@vger.kernel.org, linux-mtd@lists.infradead.org
Subject: Re: [patch] mtd: use correct error codes in debugfs_create()
Date: Mon, 22 Jul 2013 15:47:12 +0300 [thread overview]
Message-ID: <20130722124712.GG5636@mwanda> (raw)
In-Reply-To: <51ECE488.1050307@bfs.de>
The debugfs API is a bit confusing initialy but it's straight
foward to use. You call:
dfs_rootdir = debugfs_create_dir(...);
If it returns NULL then you return an error code. If debugfs is
not enabled then it returns ERR_PTR(-ENODEV) but you don't normally
need to test for it. After all later when you call:
debugfs_create_file("wear_report", S_IRUSR,
dfs_rootdir, dev, &dfs_fops);
That function is just a no-op because debugfs is disabled.
The problem here is that we test for IS_ERR_OR_NULL() instead of
just if (!dfs_rootdir) which is wrong. Also if we do hit an error
we return success because the true false bit are reversed.
regards,
dan carpenter
>
next prev parent reply other threads:[~2013-07-22 12:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-19 5:49 [patch] mtd: use correct error codes in debugfs_create() Dan Carpenter
2013-07-22 5:56 ` Dan Carpenter
2013-07-22 7:51 ` walter harms
2013-07-22 12:47 ` Dan Carpenter [this message]
2013-07-22 20:43 ` [patch v2] mtd: tiny debugfs related fixes Dan Carpenter
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=20130722124712.GG5636@mwanda \
--to=dan.carpenter@oracle.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=wharms@bfs.de \
/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