From: Miklos Szeredi <miklos@szeredi.hu>
To: akpm@linux-foundation.org
Cc: linux-kernel@vger.kernel.org
Subject: [patch 5/5] fuse: fix FUSE_FILE_OPS sending
Date: Wed, 24 Oct 2007 13:13:38 +0200 [thread overview]
Message-ID: <20071024111430.681596109@szeredi.hu> (raw)
In-Reply-To: <20071024111333.530227696@szeredi.hu>
[-- Attachment #1: fuse_file_ops_notyet.patch --]
[-- Type: text/plain, Size: 1044 bytes --]
From: Miklos Szeredi <mszeredi@suse.cz>
FUSE_FILE_OPS is meant to signal, that the kernel will send the open
file to to the userspace filesystem for operations on open files, so
that sillyrenaming unlinked files becomes unnecessary.
However this needs VFS changes, which won't make it into 2.6.24.
Signed-off-by: Miklos Szeredi <mszeredi@suse.cz>
---
Index: linux/fs/fuse/inode.c
===================================================================
--- linux.orig/fs/fuse/inode.c 2007-10-24 11:33:40.000000000 +0200
+++ linux/fs/fuse/inode.c 2007-10-24 12:10:31.000000000 +0200
@@ -579,8 +579,7 @@ static void fuse_send_init(struct fuse_c
arg->major = FUSE_KERNEL_VERSION;
arg->minor = FUSE_KERNEL_MINOR_VERSION;
arg->max_readahead = fc->bdi.ra_pages * PAGE_CACHE_SIZE;
- arg->flags |= FUSE_ASYNC_READ | FUSE_POSIX_LOCKS | FUSE_FILE_OPS |
- FUSE_ATOMIC_O_TRUNC;
+ arg->flags |= FUSE_ASYNC_READ | FUSE_POSIX_LOCKS | FUSE_ATOMIC_O_TRUNC;
req->in.h.opcode = FUSE_INIT;
req->in.numargs = 1;
req->in.args[0].size = sizeof(*arg);
--
prev parent reply other threads:[~2007-10-24 11:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-24 11:13 [patch 0/5] fuse fixes for 2.6.24 Miklos Szeredi
2007-10-24 11:13 ` [patch 1/5] fuse: fuse_file_alloc(): fix NULL dereferences Miklos Szeredi
2007-10-24 11:13 ` [patch 2/5] fuse: fix reading past EOF Miklos Szeredi
2007-10-24 11:13 ` [patch 3/5] fuse: cleanup: add fuse_get_attr_version() Miklos Szeredi
2007-10-24 11:13 ` [patch 4/5] fuse: pass open flags to read and write Miklos Szeredi
2007-10-24 11:13 ` Miklos Szeredi [this message]
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=20071024111430.681596109@szeredi.hu \
--to=miklos@szeredi.hu \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
/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
all inboxes | Powered by JetHome®