From: Ian Campbell <Ian.Campbell@citrix.com>
To: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Cc: Keir,
"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
Fraser <Keir.Fraser@eu.citrix.com>
Subject: Re: [PATCH 1 of 3] If Xen backend modules are not loaded, load them before starting Xend
Date: Tue, 22 Dec 2009 21:59:57 +0000 [thread overview]
Message-ID: <1261519197.27802.28.camel@localhost.localdomain> (raw)
In-Reply-To: <20091222195753.GB31761@phenom.dumpdata.com>
On Tue, 2009-12-22 at 19:57 +0000, Konrad Rzeszutek Wilk wrote:
> On Tue, Dec 22, 2009 at 07:41:17PM +0000, Ian Campbell wrote:
> > On Tue, 2009-12-22 at 16:48 +0000, Konrad Rzeszutek Wilk wrote:
> > > @@ -28,6 +28,7 @@
> > > grep ' xenfs$' /proc/filesystems >/dev/null && \
> > > ! grep '^xenfs ' /proc/mounts >/dev/null;
> > > then
> > > + modprobe -q xenfs
> > > mount -t xenfs xenfs /proc/xen
> > > fi
> > >
> >
> > I think this one gets requested automatically if the filesystem isn't
> > currently present, see the call to request_module in
> > fs/filesystems.c:get_fs_type()
>
> Hmm, in 2.6.32 it looks to be usuable only once the filesystem has
> loaded. This patch is for the case where the filesystem (xenfs) is compiled
> as a module - and had not been loaded. Hence hadn't had a chance to call
> fs/filesystem.c:register_filesystem().
Are you looking at __get_fs_type() and not get_fs_type()? The later is:
struct file_system_type *get_fs_type(const char *name)
{
struct file_system_type *fs;
const char *dot = strchr(name, '.');
int len = dot ? dot - name : strlen(name);
fs = __get_fs_type(name, len);
if (!fs && (request_module("%.*s", len, name) == 0))
fs = __get_fs_type(name, len);
....
So either the module is already loaded (or its statically compiled) or
it calls request_module to cause it to become loaded and the second
__get_fs_type succeeds.
> Thought maybe I messing up this up. The "grep 'xenfs$' /proc/filesystem" checks
> for xenfs in /proc/filesystem so it should not even get to the "then" statement.
Yes, the script looks wrong to me before your patch as well, the check
of /proc/filesystem should be removed.
> Something is fishy here. Why don't we skip this patch and I will revist it
> after holidays.
>
OK
Ian.
next prev parent reply other threads:[~2009-12-22 21:59 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-22 16:48 [PATCH 0 of 3] Patches when Linux Xen drivers are modules Konrad Rzeszutek Wilk
2009-12-22 16:48 ` [PATCH 1 of 3] If Xen backend modules are not loaded, load them before starting Xend Konrad Rzeszutek Wilk
2009-12-22 19:41 ` Ian Campbell
2009-12-22 19:57 ` Konrad Rzeszutek Wilk
2009-12-22 21:59 ` Ian Campbell [this message]
2009-12-22 16:48 ` [PATCH 2 of 3] [xen-detect] Return 0 if no Xen detected; 1 if running in PV context; and 2 if in HVM context Konrad Rzeszutek Wilk
2009-12-22 20:16 ` Keir Fraser
2009-12-22 16:48 ` [PATCH 3 of 3] [xen-detect] Add arguments to print out only outputs we are interested in Konrad Rzeszutek Wilk
2009-12-22 20:21 ` Keir Fraser
2009-12-22 20:26 ` Konrad Rzeszutek Wilk
2009-12-22 20:38 ` Keir Fraser
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=1261519197.27802.28.camel@localhost.localdomain \
--to=ian.campbell@citrix.com \
--cc=Keir.Fraser@eu.citrix.com \
--cc=konrad.wilk@oracle.com \
--cc=xen-devel@lists.xensource.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.