All of lore.kernel.org
 help / color / mirror / Atom feed
From: akpm@linux-foundation.org
To: nickpiggin@yahoo.com.au, mm-commits@vger.kernel.org
Subject: - fs-introduce-write_begin-write_end-and-perform_write-aops-fix-2.patch removed from -mm tree
Date: Mon, 09 Jul 2007 13:39:54 -0700	[thread overview]
Message-ID: <200707092039.l69KdsSm010067@imap1.linux-foundation.org> (raw)


The patch titled
     fs-introduce-write_begin-write_end-and-perform_write-aops-fix-2
has been removed from the -mm tree.  Its filename was
     fs-introduce-write_begin-write_end-and-perform_write-aops-fix-2.patch

This patch was dropped because it was folded into fs-introduce-write_begin-write_end-and-perform_write-aops.patch

------------------------------------------------------
Subject: fs-introduce-write_begin-write_end-and-perform_write-aops-fix-2
From: Nick Piggin <nickpiggin@yahoo.com.au>



Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
---

 fs/splice.c |    4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff -puN fs/splice.c~fs-introduce-write_begin-write_end-and-perform_write-aops-fix-2 fs/splice.c
--- a/fs/splice.c~fs-introduce-write_begin-write_end-and-perform_write-aops-fix-2
+++ a/fs/splice.c
@@ -584,7 +584,7 @@ static int pipe_to_file(struct pipe_inod
 	if (this_len + offset > PAGE_CACHE_SIZE)
 		this_len = PAGE_CACHE_SIZE - offset;
 
-	ret = pagecache_write_begin(file, mapping, sd->pos, sd->len,
+	ret = pagecache_write_begin(file, mapping, sd->pos, this_len,
 				AOP_FLAG_UNINTERRUPTIBLE, &page, &fsdata);
 	if (unlikely(ret))
 		goto out;
@@ -601,7 +601,7 @@ static int pipe_to_file(struct pipe_inod
 		kunmap_atomic(dst, KM_USER1);
 		buf->ops->unmap(pipe, buf, src);
 	}
-	ret = pagecache_write_end(file, mapping, sd->pos, sd->len, sd->len,
+	ret = pagecache_write_end(file, mapping, sd->pos, this_len, this_len,
 				page, fsdata);
 out:
 	return ret;
_

Patches currently in -mm which might be from nickpiggin@yahoo.com.au are

convert-hugetlbfs-to-use-vm_ops-fault.patch
ocfs2-release-page-lock-before-calling-page_mkwrite.patch
document-page_mkwrite-locking.patch
madvise_need_mmap_write-usage.patch
slob-initial-numa-support.patch
fs-introduce-write_begin-write_end-and-perform_write-aops.patch
fs-introduce-write_begin-write_end-and-perform_write-aops-fix-2.patch
fs-introduce-write_begin-write_end-and-perform_write-aops-fix-5.patch
gfs2-convert-to-new-aops.patch
only-allow-nonlinear-vmas-for-ram-backed-filesystems.patch
nfs-invariant-fix.patch
fs-introduce-some-page-buffer-invariants-obnoxiousness.patch
cpuset-remove-sched-domain-hooks-from-cpusets.patch
buffer-kill-old-incorrect-comment.patch
sched2-sched-domain-sysctl.patch
coredump-masking-bound-suid_dumpable-sysctl.patch
coredump-masking-reimplementation-of-dumpable-using-two-flags.patch
coredump-masking-reimplementation-of-dumpable-using-two-flags-fix.patch
coredump-masking-add-an-interface-for-core-dump-filter.patch
coredump-masking-elf-enable-core-dump-filtering.patch
coredump-masking-elf-fdpic-remove-an-unused-argument.patch
coredump-masking-elf-fdpic-enable-core-dump-filtering.patch
coredump-masking-documentation-for-proc-pid-coredump_filter.patch

                 reply	other threads:[~2007-07-09 20:40 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=200707092039.l69KdsSm010067@imap1.linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mm-commits@vger.kernel.org \
    --cc=nickpiggin@yahoo.com.au \
    /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.