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 v3] xen/debugfs: Check debugfs initialization before using it
Date: Mon, 9 Dec 2013 03:19:00 -0800 [thread overview]
Message-ID: <20131209111900.GC6562@kroah.com> (raw)
In-Reply-To: <1386583012-506-1-git-send-email-ethan.kernel@gmail.com>
On Mon, Dec 09, 2013 at 05:56:52PM +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 when debugfs not configured or disabled.
That's not what this patch does...
> Signed-off-by: ethan.zhao <ethan.kernel@gmail.com>
> ---
> arch/x86/xen/debugfs.c | 6 ++++++
> 1 file changed, 6 insertions(+)
>
> diff --git a/arch/x86/xen/debugfs.c b/arch/x86/xen/debugfs.c
> index c8377fb..85c0e0e 100644
> --- a/arch/x86/xen/debugfs.c
> +++ b/arch/x86/xen/debugfs.c
> @@ -9,12 +9,18 @@ static struct dentry *d_xen_debug;
>
> struct dentry * __init xen_init_debugfs(void)
> {
> + if (!debugfs_initialized()) {
> + d_xen_debug = NULL;
> + goto nodebugfs;
> + }
Again, why is this even needed?
What problem in the existing code are you trying to solve?
next prev parent reply other threads:[~2013-12-09 11:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-09 9:56 [PATCH v3] xen/debugfs: Check debugfs initialization before using it Ethan Zhao
2013-12-09 9:59 ` Ethan Zhao
2013-12-09 11:19 ` Greg KH [this message]
2013-12-09 13:49 ` Ethan Zhao
2013-12-09 18:39 ` 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=20131209111900.GC6562@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