From: Tejun Heo <tj@kernel.org>
To: fuse-devel@lists.sourceforge.net, miklos@szeredi.hu,
greg@kroah.com, linux-kernel@vger.kernel.org
Subject: [PATCHSET] CUSE: implement CUSE
Date: Fri, 29 Aug 2008 03:18:59 +0900 [thread overview]
Message-ID: <1219947544-666-1-git-send-email-tj@kernel.org> (raw)
This patchset implements CUSE - Character device in Userspace. Except
for initialization sequence and creation of character device instead
of a mount, CUSE isn't very different from FUSE.
This patchset is consisted of the following five patches.
0001-FUSE-add-fuse_-prefix-to-several-functions.patch
0002-FUSE-export-symbols-to-be-used-by-CUSE.patch
0003-FUSE-separate-out-fuse_conn_init-from-new_conn.patch
0004-FUSE-add-fuse_conn-release.patch
0005-CUSE-implement-CUSE-Character-device-in-Userspace.patch
0001-0004 prepares FUSE for CUSE addition and 0005 implements CUSE.
Corresponding libfuse changes will be posted separately.
This patchset is on top of...
2.6.27-rc4 (b8e6c91c74e9f0279b7c51048779b3d62da60b88)
+ [1] 9p-use-single-poller patchset
+ [2] wait-kill-is_sync_wait
+ [3] poll-allow-f_op_poll-to-sleep
+ [4] uevent updates (2 patches)
+ [5] char_dev-add-release
+ [6] extend-FUSE patchset
The above three patches allow f_op->poll() to sleep and 0007 depends
on it.
This patchset is available in the following git tree.
http://git.kernel.org/?p=linux/kernel/git/tj/misc.git;a=shortlog;h=cuse
git://git.kernel.org/pub/scm/linux/kernel/git/tj/misc.git cuse
and contains the following changes.
fs/Kconfig | 10
fs/fuse/Makefile | 1
fs/fuse/cuse.c | 634 +++++++++++++++++++++++++++++++++++++++++++++++++++
fs/fuse/dev.c | 32 +-
fs/fuse/dir.c | 34 +-
fs/fuse/file.c | 60 ++--
fs/fuse/fuse_i.h | 46 +++
fs/fuse/inode.c | 143 ++++++-----
include/linux/cuse.h | 40 +++
include/linux/fuse.h | 2
10 files changed, 882 insertions(+), 120 deletions(-)
Thanks.
--
tejun
[1] http://thread.gmane.org/gmane.linux.kernel/726098
[2] http://article.gmane.org/gmane.linux.kernel/726176
[3] http://article.gmane.org/gmane.linux.kernel/726178
[4] http://thread.gmane.org/gmane.linux.kernel/727127
[5] http://article.gmane.org/gmane.linux.kernel/727133
[6] http://thread.gmane.org/gmane.linux.kernel/727161
next reply other threads:[~2008-08-28 18:20 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-28 18:18 Tejun Heo [this message]
2008-08-28 18:19 ` [PATCH 1/5] FUSE: add fuse_ prefix to several functions Tejun Heo
2008-08-28 18:19 ` [PATCH 2/5] FUSE: export symbols to be used by CUSE Tejun Heo
2008-08-28 18:19 ` [PATCH 3/5] FUSE: separate out fuse_conn_init() from new_conn() Tejun Heo
2008-08-28 18:19 ` [PATCH 4/5] FUSE: add fuse_conn->release() Tejun Heo
2008-08-28 18:19 ` [PATCH 5/5] CUSE: implement CUSE - Character device in Userspace Tejun Heo
2008-08-28 20:07 ` Andrew Morton
2008-08-28 22:15 ` Greg KH
2008-08-28 22:32 ` Andrew Morton
2008-08-29 2:09 ` Tejun Heo
2008-08-29 2:20 ` Andrew Morton
2008-08-29 15:27 ` Nick Bowler
2008-08-29 5:50 ` [fuse-devel] [PATCHSET] CUSE: implement CUSE Mike Hommey
2008-08-29 5:52 ` Tejun Heo
2008-08-29 18:50 ` Archie Cobbs
2008-08-30 12:30 ` Tejun Heo
2008-08-30 18:56 ` Mike Hommey
2008-09-01 7:20 ` Goswin von Brederlow
2008-09-01 7:38 ` Mike Hommey
2008-08-30 22:39 ` Archie Cobbs
2008-08-31 4:52 ` hooanon05
2008-08-30 16:35 ` Goswin von Brederlow
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=1219947544-666-1-git-send-email-tj@kernel.org \
--to=tj@kernel.org \
--cc=fuse-devel@lists.sourceforge.net \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=miklos@szeredi.hu \
/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.