From: Greg KH <gregkh@linuxfoundation.org>
To: Ethan Zhao <ethan.kernel@gmail.com>
Cc: konrad.wilk@oracle.com, raghavendra.kt@linux.vnet.ibm.com,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] xen/debugfs: Check debugfs initialization before using it
Date: Mon, 9 Dec 2013 00:55:26 -0800 [thread overview]
Message-ID: <20131209085526.GB4125@kroah.com> (raw)
In-Reply-To: <CABawtvOdjncv7Zo29GbdGPm-ATsPNTVZqfje2qXTYeBRX=0w9A@mail.gmail.com>
On Mon, Dec 09, 2013 at 04:44:05PM +0800, Ethan Zhao wrote:
> On Mon, Dec 9, 2013 at 4:25 PM, Greg KH <gregkh@linuxfoundation.org> wrote:
> > On Mon, Dec 09, 2013 at 09:43:16AM +0800, Ethan Zhao wrote:
> >> On Sun, Dec 8, 2013 at 10:01 PM, Greg KH <gregkh@linuxfoundation.org> wrote:
> >> > On Sun, Dec 08, 2013 at 07:31:02PM +0800, ethan.zhao wrote:
> >> >> Should check debugfs initialization with debugfs_initialized() before using it,
> >> >> Because if it isn't initialized, the return value of fake debugfs_create_dir() etc
> >> >> functions would be ERR_PTR(-ENODEV), checking with NULL will not work.
> >> >
> >> > So? It should "just work" without this check, right? What happens if
> >> > your patch isn't applied and debugfs isn't enabled?
> >>
> >> If debugfs isn't configured, debugfs_initialized() and other
> >> functions are defined as following,
> >>
> >> static inline bool debugfs_initialized(void)
> >> {
> >> return false;
> >> }
> >>
> >> static inline struct dentry *debugfs_create_file(const char *name, umode_t mode,
> >> struct dentry *parent, void *data,
> >> const struct file_operations *fops)
> >> {
> >> return ERR_PTR(-ENODEV);
> >> }
> >>
> >> static inline struct dentry *debugfs_create_dir(const char *name,
> >> struct dentry *parent)
> >> {
> >> return ERR_PTR(-ENODEV);
> >> }
> >>
> >> And the checking code in xen\debugfs.c xen_init_debugfs() will not
> >> work, the return value is not NULL.
> >> d_xen_debug = debugfs_create_dir("xen", NULL);
> >>
> >> if (!d_xen_debug)
> >> pr_warning("Could not create 'xen' debugfs directory\n");
> >
> > Which is just fine, what is wrong with this?
>
> If we no check with debugfs_initialized(), the above code should be
> if (!d_xen_debug || IS_ERR (d_xen_debug))
> pr_warning("Could not create 'xen' debugfs directory\n");
No, you don't want to print out that message if debugfs is not enabled.
You really don't want to print anything out, as what can a user do about
this?
I still think the original code is correct, have you tried it with
debugfs disabled?
greg k-h
next prev parent reply other threads:[~2013-12-09 8:55 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-08 11:31 [PATCH] xen/debugfs: Check debugfs initialization before using it ethan.zhao
2013-12-08 14:01 ` Greg KH
2013-12-09 1:43 ` Ethan Zhao
2013-12-09 8:25 ` Greg KH
2013-12-09 8:44 ` Ethan Zhao
2013-12-09 8:55 ` Greg KH [this message]
2013-12-09 9:57 ` Ethan Zhao
2013-12-09 11:17 ` Greg KH
2013-12-09 13:42 ` Ethan Zhao
2013-12-09 18:40 ` Greg KH
2013-12-10 8:03 ` Ethan Zhao
2013-12-10 8:19 ` Greg KH
2013-12-11 2:31 ` Ethan Zhao
-- strict thread matches above, loose matches on Subject: below --
2013-12-09 10:04 Ethan Zhao
2013-12-09 11:18 ` Greg KH
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=20131209085526.GB4125@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=ethan.kernel@gmail.com \
--cc=konrad.wilk@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=raghavendra.kt@linux.vnet.ibm.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