From: David Rientjes <rientjes@google.com>
To: Shaohua Li <shaohua.li@intel.com>
Cc: Andrea Arcangeli <aarcange@redhat.com>,
Andrew Morton <akpm@linux-foundation.org>,
linux-mm <linux-mm@kvack.org>,
lkml <linux-kernel@vger.kernel.org>
Subject: Re: [patch 1/5]thp: improve the error code path
Date: Wed, 9 Nov 2011 18:43:58 -0800 (PST) [thread overview]
Message-ID: <alpine.DEB.2.00.1111091828500.32414@chino.kir.corp.google.com> (raw)
In-Reply-To: <1320892395.22361.229.camel@sli10-conroe>
On Thu, 10 Nov 2011, Shaohua Li wrote:
> > hugepage_attr_group is defined even if CONFIG_SYSFS is not set and I
> > just made a build with CONFIG_SYSFS=n and it builds just fine without
> > any change.
>
> > $ grep CONFIG_SYSFS .config
> > # CONFIG_SYSFS is not set
> >
> > So we can drop 1/5 above.
> this isn't the case in the code. And the code uses hugepage_attr_group
> is already within CONFIG_SYSFS, so your build success.
>
You're right, but I agree that the #ifdef's just make the function error
handling much too complex. Would you mind adding sysfs_*_out labels at
the end of the function to handle these errors instead? And I think we
should be doing khugepaged_slab_init() and mm_slots_hash_init() before
initializing sysfs.
Something like
out:
khugepaged_slab_free();
mm_slots_hash_free(); <-- after you remove it from #if 0
return err;
#ifdef CONFIG_SYSFS
sysfs_khugepaged_out:
sysfs_remove_group(hugepage_kobj, &khugepaged_attr_group);
sysfs_hugepage_out:
sysfs_remove_group(hugepage_kobj, &hugepage_attr_group);
...
goto out;
#endif
--
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:[~2011-11-10 2:44 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-25 2:58 Shaohua Li
2011-10-25 11:44 ` Andrea Arcangeli
2011-10-26 1:48 ` Shaohua Li
2011-11-07 5:17 ` Shaohua Li
2011-11-10 2:18 ` Andrea Arcangeli
2011-11-10 2:33 ` Shaohua Li
2011-11-10 2:43 ` David Rientjes [this message]
2011-11-10 3:06 ` Andrea Arcangeli
2011-11-10 4:43 ` David Rientjes
2011-11-10 5:56 ` Shaohua Li
2011-11-10 6:08 ` David Rientjes
2011-11-10 6:27 ` Shaohua Li
2011-11-10 14:14 ` Andrea Arcangeli
2011-11-11 6:33 ` Shaohua Li
2011-11-11 6:50 ` Andrea Arcangeli
2011-11-10 2:59 ` Andrea Arcangeli
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=alpine.DEB.2.00.1111091828500.32414@chino.kir.corp.google.com \
--to=rientjes@google.com \
--cc=aarcange@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=shaohua.li@intel.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