From: Theodore Tso <tytso@mit.edu>
To: Mingming Cao <cmm@us.ibm.com>
Cc: Badari Pulavarty <pbadari@gmail.com>,
markn@au1.ibm.com, ext4 <linux-ext4@vger.kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
"Amit K. Arora" <aarora@linux.vnet.ibm.com>,
"Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com>
Subject: Re: [patch 1/2] add init_ext4_proc() stub for when CONFIG_PROC_FS is not set
Date: Tue, 9 Oct 2007 20:22:05 -0400 [thread overview]
Message-ID: <20071010002203.GL31713@thunk.org> (raw)
In-Reply-To: <20071009174012.GJ31713@thunk.org>
On Tue, Oct 09, 2007 at 01:40:12PM -0400, Theodore Tso wrote:
> On Tue, Oct 09, 2007 at 10:03:06AM -0700, Mingming Cao wrote:
> > I guess our testing did not catch this up because we have CONFIG_PROC_FS
> > enabled all the time. mballoc needs procfs for exporting some stats info
> > and tunable paramenters to optimize/customize multiple allocation.
> >
> > We could select CONFIG_PROC_FS at kconfig when ext4dev is enabled.
>
> We definitely should be able to compile without CONFIG_PROC_FS; it's a
> major flaw in the mballoc-core.patch that it doesn't work without it.
I will fold the following into mballoc-core.patch. It's sufficient to
allow us to compile w/o CONFIG_PROC_FS defined.
- Ted
diff --git a/fs/ext4/mballoc.c b/fs/ext4/mballoc.c
index 4409c0c..2305af4 100644
--- a/fs/ext4/mballoc.c
+++ b/fs/ext4/mballoc.c
@@ -2854,9 +2854,11 @@ int __init init_ext4_proc(void)
if (ext4_pspace_cachep == NULL)
return -ENOMEM;
+#ifdef CONFIG_PROC_FS
proc_root_ext4 = proc_mkdir(EXT4_ROOT, proc_root_fs);
if (proc_root_ext4 == NULL)
printk(KERN_ERR "EXT4-fs: Unable to create %s\n", EXT4_ROOT);
+#endif
return 0;
}
@@ -2865,7 +2867,9 @@ void exit_ext4_proc(void)
{
/* XXX: synchronize_rcu(); */
kmem_cache_destroy(ext4_pspace_cachep);
+#ifdef CONFIG_PROC_FS
remove_proc_entry(EXT4_ROOT, proc_root_fs);
+#endif
}
next prev parent reply other threads:[~2007-10-10 0:22 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-09 5:50 [patch 0/2] ext4 fixups for 2.6.23-rc8-mm2/ext4 git tree markn
2007-10-09 5:50 ` [patch 1/2] add init_ext4_proc() stub for when CONFIG_PROC_FS is not set markn
2007-10-09 16:31 ` Badari Pulavarty
2007-10-09 17:03 ` Mingming Cao
2007-10-09 17:28 ` Badari Pulavarty
2007-10-09 17:40 ` Theodore Tso
2007-10-10 0:22 ` Theodore Tso [this message]
2007-10-10 15:30 ` Badari Pulavarty
2007-10-10 19:00 ` Theodore Tso
2007-10-11 20:00 ` Badari Pulavarty
2007-10-10 0:22 ` Mark Nelson
2007-10-09 5:50 ` [patch 2/2] move init_ext4_proc() last and add cleanup call exit_ext4_proc() markn
2007-10-09 16:22 ` Badari Pulavarty
2007-10-10 0:11 ` Mark Nelson
2007-10-10 0:34 ` Theodore Tso
2007-10-10 0:41 ` Theodore Tso
2007-10-10 0:50 ` Mark Nelson
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=20071010002203.GL31713@thunk.org \
--to=tytso@mit.edu \
--cc=aarora@linux.vnet.ibm.com \
--cc=akpm@linux-foundation.org \
--cc=aneesh.kumar@linux.vnet.ibm.com \
--cc=cmm@us.ibm.com \
--cc=linux-ext4@vger.kernel.org \
--cc=markn@au1.ibm.com \
--cc=pbadari@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.