From: Sasikanth babu <sasikanth.v19@gmail.com>
To: David Rientjes <rientjes@google.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Mel Gorman <mel@csn.ul.ie>, Christoph Lameter <cl@linux.com>,
KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] mm:vmstat - Removed debug fs entries on failure of file creation and made extfrag_debug_root dentry local
Date: Tue, 24 Apr 2012 02:45:54 +0530 [thread overview]
Message-ID: <CAOJFanXaX__QZmbs15e04g6D-0478cAjm70WZK-BWebJCuQCQw@mail.gmail.com> (raw)
In-Reply-To: <alpine.DEB.2.00.1204231334200.11602@chino.kir.corp.google.com>
[-- Attachment #1: Type: text/plain, Size: 1998 bytes --]
On Tue, Apr 24, 2012 at 2:05 AM, David Rientjes <rientjes@google.com> wrote:
> On Tue, 24 Apr 2012, Sasikantha babu wrote:
>
> > diff --git a/mm/vmstat.c b/mm/vmstat.c
> > index f600557..ddae476 100644
> > --- a/mm/vmstat.c
> > +++ b/mm/vmstat.c
> > @@ -1220,7 +1220,6 @@ module_init(setup_vmstat)
> > #if defined(CONFIG_DEBUG_FS) && defined(CONFIG_COMPACTION)
> > #include <linux/debugfs.h>
> >
> > -static struct dentry *extfrag_debug_root;
> >
> > /*
> > * Return an index indicating how much of the available free memory is
> > @@ -1358,17 +1357,23 @@ static const struct file_operations
> extfrag_file_ops = {
> >
> > static int __init extfrag_debug_init(void)
> > {
> > + struct dentry *extfrag_debug_root;
> > +
> > extfrag_debug_root = debugfs_create_dir("extfrag", NULL);
> > if (!extfrag_debug_root)
> > return -ENOMEM;
> >
> > if (!debugfs_create_file("unusable_index", 0444,
> > - extfrag_debug_root, NULL, &unusable_file_ops))
> > + extfrag_debug_root, NULL, &unusable_file_ops)) {
> > + debugfs_remove (extfrag_debug_root);
> > return -ENOMEM;
> > + }
> >
> > if (!debugfs_create_file("extfrag_index", 0444,
> > - extfrag_debug_root, NULL, &extfrag_file_ops))
> > + extfrag_debug_root, NULL, &extfrag_file_ops)) {
> > + debugfs_remove_recursive (extfrag_debug_root);
> > return -ENOMEM;
> > + }
> >
> > return 0;
> > }
>
> Probably easier to do something like "goto fail" and then have a
>
> return 0;
>
> fail:
> debugfs_remove_recursive(extfrag_debug_root);
> return -ENOMEM;
>
> Thanks, i will do the modification and resend the patch
> at the end of the function.
>
> Please run scripts/checkpatch.pl on your patch before proposing it.
>
Didnt notice extra space after fucntion. From now onwards will run
checkpatch Thanks
[-- Attachment #2: Type: text/html, Size: 2896 bytes --]
next prev parent reply other threads:[~2012-04-23 21:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-23 19:08 Sasikantha babu
2012-04-23 20:35 ` David Rientjes
2012-04-23 21:15 ` Sasikanth babu [this message]
-- strict thread matches above, loose matches on Subject: below --
2012-04-23 18:50 Sasikanth V
2012-04-23 19:08 ` KOSAKI Motohiro
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=CAOJFanXaX__QZmbs15e04g6D-0478cAjm70WZK-BWebJCuQCQw@mail.gmail.com \
--to=sasikanth.v19@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=cl@linux.com \
--cc=kosaki.motohiro@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mel@csn.ul.ie \
--cc=rientjes@google.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