From: Sasikanth babu <sasikanth.v19@gmail.com>
To: Andrew Morton <akpm@linux-foundation.org>
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: Sun, 29 Apr 2012 01:15:37 +0530 [thread overview]
Message-ID: <CAOJFanXUdy17kcRHnOuHv5fgv44b4LrwviPupCEx9BbY6QF=zg@mail.gmail.com> (raw)
In-Reply-To: <20120428120657.4982a248.akpm@linux-foundation.org>
[-- Attachment #1: Type: text/plain, Size: 2035 bytes --]
On Sun, Apr 29, 2012 at 12:36 AM, Andrew Morton
<akpm@linux-foundation.org>wrote:
> On Sun, 29 Apr 2012 00:32:26 +0530 Sasikanth babu <sasikanth.v19@gmail.com>
> wrote:
>
> > > 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.
> > >
> >
> > I'm working on a patch which address this issue. debugfs_create_XXX
> > calls
> > will return proper error codes, and fixing the existing code not each
> > and every part but the code
> > which handles the values returned by debufs_create_XXX otherwise it
> will
> > break the existing
> > functionality .
>
> Excellent!
>
> > (any suggestions or opinions ?)
>
> Well, don't modify the existing interfaces: create new ones and we can
> migrate gradually. But you're probably already doing that.
>
Not going to change the existing interface. Modified debugfs_create_XXX
to return ERR_PTR(error) instead of NULL.
[sasikantha@localhost linux-2.6]$ git diff
diff --git a/fs/debugfs/inode.c b/fs/debugfs/inode.c
index b80bc84..f5a5783 100644
--- a/fs/debugfs/inode.c
+++ b/fs/debugfs/inode.c
@@ -378,7 +378,7 @@ struct dentry *debugfs_create_file(const char *name,
umode_t mode,
error = debugfs_create_by_name(name, mode, parent, &dentry,
data, fops);
if (error) {
- dentry = NULL;
+ dentry = ERR_PTR(error);
simple_release_fs(&debugfs_mount, &debugfs_mount_count);
goto exit;
}
And from the caller side modifying the code as shown below (Currently
started doing
modification for each subsystem)
dir = debugfs_create_dir("test", NULL);
if (IS_ERR(dir)) {
return PTR_ERR(dir);
}
I think as you had mentioned creating new interface and migrating
gradually is the right of
way of doing it.
Thanks
Sasi
[-- Attachment #2: Type: text/html, Size: 2684 bytes --]
prev parent reply other threads:[~2012-04-28 19:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-25 19:59 Sasikantha babu
2012-04-26 23:21 ` Andrew Morton
2012-04-28 19:02 ` Sasikanth babu
2012-04-28 19:06 ` Andrew Morton
2012-04-28 19:45 ` Sasikanth babu [this message]
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='CAOJFanXUdy17kcRHnOuHv5fgv44b4LrwviPupCEx9BbY6QF=zg@mail.gmail.com' \
--to=sasikanth.v19@gmail.com \
--cc=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=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