From: Mark Fasheh <mark.fasheh@oracle.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] Re: Announce: new-aops-1 for 2.6.21-rc3
Date: Thu, 15 Mar 2007 14:08:48 -0700 [thread overview]
Message-ID: <20070315210848.GG21942@ca-server1.us.oracle.com> (raw)
In-Reply-To: <20070315161704.GH8321@wotan.suse.de>
On Thu, Mar 15, 2007 at 05:17:04PM +0100, Nick Piggin wrote:
> OK, I've gone through and fixed several bugs until the thing actually
> survives fsx-linux for both ext2 and ext3 ordered and writeback (both
> when using the new aops, and the legacy prepare_write path). Actually
> ext3 sometimes breaks, but it does in unpatched kernels anyway.
Attached is a bugfix for a crash folks who use an initrd will hit early on.
--Mark
--
Mark Fasheh
Senior Software Developer, Oracle
mark.fasheh at oracle.com
From: Mark Fasheh <mark.fasheh@oracle.com>
[PATCH] Populate pagep in simple_write_begin()
This wasn't getting passed back to callers.
Signed-off-by: Mark Fasheh <mark.fasheh@oracle.com>
cbf20bf51ddd6434db935ba29f845a85f3b1ec65
diff --git a/fs/libfs.c b/fs/libfs.c
index 51f9748..602496a 100644
--- a/fs/libfs.c
+++ b/fs/libfs.c
@@ -357,6 +357,8 @@ int simple_write_begin(struct file *file
if (!page)
return -ENOMEM;
+ *pagep = page;
+
return simple_prepare_write(file, page, from, from+len);
}
--
1.3.3
next prev parent reply other threads:[~2007-03-15 21:08 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-15 16:17 [Cluster-devel] Announce: new-aops-1 for 2.6.21-rc3 Nick Piggin
2007-03-15 16:17 ` Nick Piggin
2007-03-15 19:32 ` [Cluster-devel] " Joel Becker
2007-03-15 19:57 ` Nick Piggin
2007-03-15 19:53 ` Mark Fasheh
2007-03-15 19:57 ` Nick Piggin
2007-03-15 21:08 ` Mark Fasheh [this message]
2007-03-15 23:47 ` Mark Fasheh
2007-03-20 5:36 ` Nick Piggin
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=20070315210848.GG21942@ca-server1.us.oracle.com \
--to=mark.fasheh@oracle.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;
as well as URLs for NNTP newsgroup(s).