From: Rusty Lynch <rusty@linux.co.intel.com>
To: ocfs2-devel@oss.oracle.com
Subject: [Ocfs2-devel] [PATCH]Enable 2.6 file data flushing
Date: Tue Mar 23 23:59:07 2004 [thread overview]
Message-ID: <20040324055857.GA14337@penguin.co.intel.com> (raw)
In-Reply-To: <20040324042306.GE1516@ca-server1.us.oracle.com>
On Tue, Mar 23, 2004 at 08:23:06PM -0800, Wim Coekaerts wrote:
> hmm now I wonder if we dont' also need that in 2.4...
>
>
> On Tue, Mar 23, 2004 at 08:11:53PM -0800, Rusty Lynch wrote:
> > The following small patch makes a 2.6 built kernel flush it's
> > data buffers to disk on ocfs_sync_inode, fixing bug #46
> >
> > http://oss.oracle.com/bugzilla/show_bug.cgi?id=46
> >
> > --rusty
> >
the equivilant call in 2.4 would be filemap_fdatasync(). I gave it a
try and it does fix the mmap issue talked about in bug #50.
Here is a patch
Index: src/file.c
===================================================================
--- src/file.c (revision 807)
+++ src/file.c (working copy)
@@ -68,8 +68,10 @@
{
int status;
#if LINUX_VERSION_CODE >= KERNEL_VERSION(2,6,0)
+ filemap_fdatawrite(inode->i_mapping);
status = sync_mapping_buffers(inode->i_mapping);
#else
+ filemap_fdatasync(inode->i_mapping);
status = fsync_inode_buffers(inode);
#if LINUX_VERSION_CODE >= KERNEL_VERSION(2,4,18)
if (!status)
next prev parent reply other threads:[~2004-03-23 23:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-23 22:11 [Ocfs2-devel] [PATCH]Enable 2.6 file data flushing Rusty Lynch
2004-03-23 22:23 ` Wim Coekaerts
2004-03-23 23:59 ` Rusty Lynch [this message]
2004-03-24 3:40 ` Wim Coekaerts
2004-03-24 16:37 ` Mark Fasheh
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=20040324055857.GA14337@penguin.co.intel.com \
--to=rusty@linux.co.intel.com \
--cc=ocfs2-devel@oss.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 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.