From: Greg KH <gregkh@linuxfoundation.org>
To: Ethan Zhao <ethan.kernel@gmail.com>
Cc: konrad.wilk@oracle.com, raghavendra.kt@linux.vnet.ibm.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] xen/debugfs: Check debugfs initialization before using it
Date: Mon, 9 Dec 2013 03:18:17 -0800 [thread overview]
Message-ID: <20131209111817.GB6562@kroah.com> (raw)
In-Reply-To: <1386583443-568-1-git-send-email-ethan.kernel@gmail.com>
On Mon, Dec 09, 2013 at 06:04:03PM +0800, Ethan Zhao wrote:
> From: "Ethan Zhao" <ethan.kernel@gmail.com>
>
> 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.
>
> V3: Add warning message about debugfs not configured or disabled.
>
> Signed-off-by: Ethan Zhao <ethan.kernel@gmail.com>
> ---
> arch/x86/xen/debugfs.c | 7 +++++++
> 1 file changed, 7 insertions(+)
>
> diff --git a/arch/x86/xen/debugfs.c b/arch/x86/xen/debugfs.c
> index c8377fb..033a5dd 100644
> --- a/arch/x86/xen/debugfs.c
> +++ b/arch/x86/xen/debugfs.c
> @@ -9,12 +9,19 @@ static struct dentry *d_xen_debug;
>
> struct dentry * __init xen_init_debugfs(void)
> {
> + if (!debugfs_initialized()) {
> + d_xen_debug = NULL;
> + pr_warning("debugfs is not configured or enabled\n");
No, again, don't say anything, this is useless, just leave the code
as-is, it isn't causing any problems, is it?
gre gk-h
next prev parent reply other threads:[~2013-12-09 11:16 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-09 10:04 [PATCH] xen/debugfs: Check debugfs initialization before using it Ethan Zhao
2013-12-09 11:18 ` Greg KH [this message]
-- strict thread matches above, loose matches on Subject: below --
2013-12-08 11:31 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
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
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=20131209111817.GB6562@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