reiserfs-devel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Edward Shishkin <edward.shishkin@gmail.com>
To: akpm@linux-foundation.org
Cc: jens.axboe@oracle.com,
	ReiserFS Mailing List <reiserfs-devel@vger.kernel.org>
Subject: [patch] reiser4: specify splice file operations
Date: Tue, 04 Dec 2007 19:44:27 +0300	[thread overview]
Message-ID: <475583EB.4050608@gmail.com> (raw)
In-Reply-To: <200710212347.l9LNlD6K000649@imap1.linux-foundation.org>

[-- Attachment #1: Type: text/plain, Size: 476 bytes --]

akpm@linux-foundation.org wrote:

>The patch titled
>     git-block-vs-reiser4
>has been removed from the -mm tree.  Its filename was
>     git-block-vs-reiser4.patch
>
>This patch was dropped because it was folded into reiser4.patch
>
>------------------------------------------------------
>Subject: git-block-vs-reiser4
>From: Andrew Morton
>
>Hope this is right.
>
>Hope you know what you're doing ;)
>

This is a fixup for broken loopback functionality.

Thanks,
Edward.

[-- Attachment #2: reiser4-specify-splice_ops.patch --]
[-- Type: text/x-patch, Size: 1295 bytes --]

Specify splice_read, splice_write file operations for
loopback functionality.

Signed-off-by: Edward Shishkin <edward.shishkin@gmail.com>
---
 linux-2.6.24-rc3-mm2/fs/reiser4/plugin/file/cryptcompress.c |    3 ++-
 linux-2.6.24-rc3-mm2/fs/reiser4/plugin/object.c             |    4 +++-
 2 files changed, 5 insertions(+), 2 deletions(-)

--- linux-2.6.24-rc3-mm2/fs/reiser4/plugin/file/cryptcompress.c.orig
+++ linux-2.6.24-rc3-mm2/fs/reiser4/plugin/file/cryptcompress.c
@@ -3747,13 +3747,14 @@
 int prepare_write_cryptcompress(struct file *file, struct page *page,
 				unsigned from, unsigned to)
 {
-	return 0;
+	return -EINVAL;
 }
 
 /* plugin->commit_write */
 int commit_write_cryptcompress(struct file *file, struct page *page,
 			       unsigned from, unsigned to)
 {
+	BUG();
 	return 0;
 }
 
--- linux-2.6.24-rc3-mm2/fs/reiser4/plugin/object.c.orig
+++ linux-2.6.24-rc3-mm2/fs/reiser4/plugin/object.c
@@ -103,7 +103,9 @@
 	.mmap = reiser4_mmap_careful,
 	.open = reiser4_open_careful,
 	.release = reiser4_release_careful,
-	.fsync = reiser4_sync_file_common
+	.fsync = reiser4_sync_file_common,
+	.splice_read = generic_file_splice_read,
+	.splice_write = generic_file_splice_write
 };
 static struct address_space_operations regular_file_a_ops = {
 	.writepage = reiser4_writepage,

           reply	other threads:[~2007-12-04 16:44 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <200710212347.l9LNlD6K000649@imap1.linux-foundation.org>]

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=475583EB.4050608@gmail.com \
    --to=edward.shishkin@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=jens.axboe@oracle.com \
    --cc=reiserfs-devel@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;
as well as URLs for NNTP newsgroup(s).