From: Andrew Morton <akpm@linux-foundation.org>
To: Sasikantha babu <sasikanth.v19@gmail.com>
Cc: Tejun Heo <tj@kernel.org>, "H. Peter Anvin" <hpa@linux.intel.com>,
Ingo Molnar <mingo@elte.hu>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] mm: memblock - Handled failure of debug fs entries creation
Date: Thu, 26 Apr 2012 16:21:08 -0700 [thread overview]
Message-ID: <20120426162108.b654a920.akpm@linux-foundation.org> (raw)
In-Reply-To: <1335383992-19419-1-git-send-email-sasikanth.v19@gmail.com>
On Thu, 26 Apr 2012 01:29:52 +0530
Sasikantha babu <sasikanth.v19@gmail.com> wrote:
> 1) Removed already created debug fs entries on failure
>
> 2) Fixed coding style 80 char per line
>
> Signed-off-by: Sasikantha babu <sasikanth.v19@gmail.com>
> ---
> mm/memblock.c | 14 +++++++++++---
> 1 files changed, 11 insertions(+), 3 deletions(-)
>
> diff --git a/mm/memblock.c b/mm/memblock.c
> index a44eab3..5553723 100644
> --- a/mm/memblock.c
> +++ b/mm/memblock.c
> @@ -966,11 +966,19 @@ static int __init memblock_init_debugfs(void)
> {
> struct dentry *root = debugfs_create_dir("memblock", NULL);
> if (!root)
> - return -ENXIO;
> - debugfs_create_file("memory", S_IRUGO, root, &memblock.memory, &memblock_debug_fops);
> - debugfs_create_file("reserved", S_IRUGO, root, &memblock.reserved, &memblock_debug_fops);
> + return -ENOMEM;
hm, why the switch to -ENOMEM?
Fact is, debugfs_create_dir() and debugfs_create_file() are stupid
interfaces which don't provide the caller (and hence the user) with any
information about why they failed. Perhaps memblock_init_debugfs()
should return -EWESUCK.
> + if (!debugfs_create_file("memory", S_IRUGO, root, &memblock.memory,
> + &memblock_debug_fops))
> + goto fail;
> + if (!debugfs_create_file("reserved", S_IRUGO, root, &memblock.reserved,
> + &memblock_debug_fops))
> + goto fail;
>
> return 0;
> +fail:
> + debugfs_remove_recursive(root);
> + return -ENOMEM;
> }
> __initcall(memblock_init_debugfs);
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Fight unfair telecom internet charges in Canada: sign http://stopthemeter.ca/
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2012-04-26 23:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-25 19:59 [PATCH 2/2] mm: memblock - Handled failure of debug fs entries creation Sasikantha babu
2012-04-26 23:21 ` Andrew Morton [this message]
2012-04-28 19:02 ` Sasikanth babu
2012-04-28 19:06 ` Andrew Morton
2012-04-28 19:45 ` Sasikanth babu
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=20120426162108.b654a920.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=hpa@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mingo@elte.hu \
--cc=sasikanth.v19@gmail.com \
--cc=tj@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).