From: Ingo Molnar <mingo@elte.hu>
To: Jeremy Fitzhardinge <jeremy@goop.org>
Cc: Al Viro <viro@ftp.linux.org.uk>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Xen-devel <xen-devel@lists.xensource.com>,
Alex Zeffertt <alex.zeffertt@eu.citrix.com>,
Ian Campbell <Ian.Campbell@citrix.com>,
Christoph Hellwig <hch@infradead.org>
Subject: Re: [PATCH] xen: add xenfs to allow usermode <-> Xen interaction
Date: Tue, 16 Dec 2008 21:46:16 +0100 [thread overview]
Message-ID: <20081216204616.GC14787@elte.hu> (raw)
In-Reply-To: <49480F39.2010102@goop.org>
* Jeremy Fitzhardinge <jeremy@goop.org> wrote:
> [ Reviewers: This is in drivers/xen to keep it close to the code it is
> and will be using. Would people prefer to see it in fs/xenfs? -J ]
> +config XENFS
> + tristate "Xen filesystem"
there's about two dozen filesystems that live not in fs/*:
./net/socket.c: register_filesystem(&sock_fs_type);
./net/sunrpc/rpc_pipe.c: err = register_filesystem(&rpc_pipe_fs_type);
./security/selinux/selinuxfs.c: err = register_filesystem(&sel_fs_type);
./security/inode.c: retval = register_filesystem(&fs_type);
./security/smack/smackfs.c: err = register_filesystem(&smk_fs_type);
./drivers/usb/core/inode.c: retval = register_filesystem(&usb_fs_type);
./drivers/usb/gadget/inode.c: status = register_filesystem (&gadgetfs_type);
./drivers/oprofile/oprofilefs.c: return register_filesystem(&oprofilefs_type);
./drivers/misc/ibmasm/ibmasmfs.c: return register_filesystem(&ibmasmfs_type);
./drivers/isdn/capi/capifs.c: err = register_filesystem(&capifs_fs_type);
./drivers/infiniband/hw/ipath/ipath_fs.c: return register_filesystem(&ipathfs_fs_type);
./drivers/infiniband/core/uverbs_main.c: ret = register_filesystem(&uverbs_event_fs);
./mm/shmem.c: error = register_filesystem(&tmpfs_fs_type);
./mm/tiny-shmem.c: BUG_ON(register_filesystem(&tmpfs_fs_type) != 0);
./ipc/mqueue.c: error = register_filesystem(&mqueue_fs_type);
./kernel/cpuset.c: err = register_filesystem(&cpuset_fs_type);
./kernel/cgroup.c: err = register_filesystem(&cgroup_fs_type);
./include/linux/fs.h:extern int register_filesystem(struct file_system_type *);
./arch/s390/hypfs/inode.c: rc = register_filesystem(&hypfs_type);
./arch/ia64/kernel/perfmon.c: int err = register_filesystem(&pfm_fs_type);
./arch/powerpc/platforms/cell/spufs/inode.c: ret = register_filesystem(&spufs_type);
by the looks of it it wants to live in drivers/xen/. It's a minimalistic
API-only filesystem.
Nevertheless it would be nice to have Acks from FS experts. Security,
races, obsoleteness of approach, etc.
Ingo
next prev parent reply other threads:[~2008-12-16 20:46 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-16 20:27 [PATCH] xen: add xenfs to allow usermode <-> Xen interaction Jeremy Fitzhardinge
2008-12-16 20:46 ` Ingo Molnar [this message]
2008-12-16 20:54 ` Andrew Morton
2008-12-16 22:43 ` Jeremy Fitzhardinge
2008-12-17 21:24 ` [PATCH UPDATED] " Jeremy Fitzhardinge
2008-12-17 21:34 ` Andrew Morton
2008-12-17 21:50 ` Jeremy Fitzhardinge
2008-12-18 13:18 ` Ingo Molnar
2008-12-17 21:40 ` [PATCH UPDATED] xen/xenfs: fix xenbus message reads Jeremy Fitzhardinge
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=20081216204616.GC14787@elte.hu \
--to=mingo@elte.hu \
--cc=Ian.Campbell@citrix.com \
--cc=akpm@linux-foundation.org \
--cc=alex.zeffertt@eu.citrix.com \
--cc=hch@infradead.org \
--cc=jeremy@goop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=viro@ftp.linux.org.uk \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox