From: "Serge E. Hallyn" <serue@us.ibm.com>
To: Randy Dunlap <randy.dunlap@oracle.com>
Cc: linux-kernel@vger.kernel.org, Andrew Morton <akpm@linux-foundation.org>
Subject: Re: mmotm 2009-02-24-16-23 uploaded (proc_net & namespaces)
Date: Wed, 25 Feb 2009 11:17:48 -0600 [thread overview]
Message-ID: <20090225171748.GC14463@us.ibm.com> (raw)
In-Reply-To: <49A5778E.1000204@oracle.com>
Quoting Randy Dunlap (randy.dunlap@oracle.com):
> akpm@linux-foundation.org wrote:
> > The mm-of-the-moment snapshot 2009-02-24-16-23 has been uploaded to
> >
> > http://userweb.kernel.org/~akpm/mmotm/
> >
> > and will soon be available at
> >
> > git://git.zen-sources.org/zen/mmotm.git
> >
> > It contains the following patches against 2.6.29-rc6:
>
> namespaces-move-proc_net_get_sb-to-a-generic-fs-superc-helper.patch,
> when CONFIG_NAMESPACES=n:
>
> proc_net.c:(.text+0x4255c): undefined reference to `get_sb_ns'
>
>
> config attached.
Thanks, Randy. Does the following fix it?
(Sorry, it's a misleading patch, and maybe it would turn out more
readable if I moved get_sb_ns under instead of above the
CONFIG_BLOCK ifdef... But all I'm doing is what the subject says,
plus adding an EXPORT_SYMBOL which may be debatable, but is in
keeping with other get_sb_*'s.)
thanks,
-serge
>From fff28e37112037efbbc6e44e29bbd741c9dd38a9 Mon Sep 17 00:00:00 2001
From: Serge E. Hallyn <serue@us.ibm.com>
Date: Wed, 25 Feb 2009 09:14:03 -0800
Subject: [PATCH 1/1] namespaces: get_sb_ns does not require CONFIG_BLOCK
So move it outside of the CONFIG_BLOCK ifdef in fs/super.c.
Signed-off-by: Serge E. Hallyn <serue@us.ibm.com>
---
fs/super.c | 50 ++++++++++++++++++++++++++------------------------
1 files changed, 26 insertions(+), 24 deletions(-)
diff --git a/fs/super.c b/fs/super.c
index 1a37b58..b3bf049 100644
--- a/fs/super.c
+++ b/fs/super.c
@@ -761,30 +761,6 @@ void kill_litter_super(struct super_block *sb)
EXPORT_SYMBOL(kill_litter_super);
-#ifdef CONFIG_BLOCK
-static int set_bdev_super(struct super_block *s, void *data)
-{
- s->s_bdev = data;
- s->s_dev = s->s_bdev->bd_dev;
- return 0;
-}
-
-static int test_bdev_super(struct super_block *s, void *data)
-{
- return (void *)s->s_bdev == data;
-}
-
-static int ns_test_super(struct super_block *sb, void *data)
-{
- return sb->s_fs_info == data;
-}
-
-static int ns_set_super(struct super_block *sb, void *data)
-{
- sb->s_fs_info = data;
- return set_anon_super(sb, NULL);
-}
-
int get_sb_ns(struct file_system_type *fs_type, int flags, void *data,
int (*fill_super)(struct super_block *, void *, int),
struct vfsmount *mnt)
@@ -812,6 +788,32 @@ int get_sb_ns(struct file_system_type *fs_type, int flags, void *data,
return 0;
}
+EXPORT_SYMBOL(get_sb_ns);
+
+#ifdef CONFIG_BLOCK
+static int set_bdev_super(struct super_block *s, void *data)
+{
+ s->s_bdev = data;
+ s->s_dev = s->s_bdev->bd_dev;
+ return 0;
+}
+
+static int test_bdev_super(struct super_block *s, void *data)
+{
+ return (void *)s->s_bdev == data;
+}
+
+static int ns_test_super(struct super_block *sb, void *data)
+{
+ return sb->s_fs_info == data;
+}
+
+static int ns_set_super(struct super_block *sb, void *data)
+{
+ sb->s_fs_info = data;
+ return set_anon_super(sb, NULL);
+}
+
int get_sb_bdev(struct file_system_type *fs_type,
int flags, const char *dev_name, void *data,
int (*fill_super)(struct super_block *, void *, int),
--
1.5.4.3
next prev parent reply other threads:[~2009-02-25 17:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200902250041.n1P0fe4A024914@imap1.linux-foundation.org>
2009-02-25 16:47 ` mmotm 2009-02-24-16-23 uploaded (intel_cacheinfo) Randy Dunlap
2009-02-25 16:53 ` mmotm 2009-02-24-16-23 uploaded (proc_net & namespaces) Randy Dunlap
2009-02-25 17:17 ` Serge E. Hallyn [this message]
2009-02-25 17:28 ` Randy Dunlap
2009-02-25 17:47 ` Serge E. Hallyn
2009-02-25 18:10 ` Randy Dunlap
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=20090225171748.GC14463@us.ibm.com \
--to=serue@us.ibm.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=randy.dunlap@oracle.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