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 12:53:51 -0700 [thread overview]
Message-ID: <20070315195351.GE21942@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.
>
> At 15 patches (including the initial buffered write deadlock fixes),
> it is too much to keep posting -- not much has fundamentally changed,
> so I'll just post occasionally if we make big changes. The quilt
> format is probably easier for someone wishing to work on it anyway.
Hmm, we still left out some exports...
--Mark
--
Mark Fasheh
Senior Software Developer, Oracle
mark.fasheh at oracle.com
From: Mark Fasheh <mark.fasheh@oracle.com>
[PATCH] Export simple_write_begin, simple_write_end
These are used by configfs, which can be built as a module.
Signed-off-by: Mark Fasheh <mark.fasheh@oracle.com>
---
fs/libfs.c | 2 ++
1 files changed, 2 insertions(+), 0 deletions(-)
36f5d6a135c9f3f30fee3d0e4ffa887e1803ac95
diff --git a/fs/libfs.c b/fs/libfs.c
index d687819..51f9748 100644
--- a/fs/libfs.c
+++ b/fs/libfs.c
@@ -656,6 +656,8 @@ EXPORT_SYMBOL(dcache_dir_open);
EXPORT_SYMBOL(dcache_readdir);
EXPORT_SYMBOL(generic_read_dir);
EXPORT_SYMBOL(get_sb_pseudo);
+EXPORT_SYMBOL(simple_write_begin);
+EXPORT_SYMBOL(simple_write_end);
EXPORT_SYMBOL(simple_commit_write);
EXPORT_SYMBOL(simple_dir_inode_operations);
EXPORT_SYMBOL(simple_dir_operations);
--
1.3.3
WARNING: multiple messages have this Message-ID (diff)
From: Mark Fasheh <mark.fasheh@oracle.com>
To: Nick Piggin <npiggin@suse.de>
Cc: jfs-discussion@lists.sourceforge.net, xfs@oss.sgi.com,
cluster-devel@redhat.com, reiserfs-list@namesys.com,
nfs@lists.sourceforge.net,
Linux Filesystems <linux-fsdevel@vger.kernel.org>,
linux-ext4@vger.kernel.org
Subject: Re: Announce: new-aops-1 for 2.6.21-rc3
Date: Thu, 15 Mar 2007 12:53:51 -0700 [thread overview]
Message-ID: <20070315195351.GE21942@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.
>
> At 15 patches (including the initial buffered write deadlock fixes),
> it is too much to keep posting -- not much has fundamentally changed,
> so I'll just post occasionally if we make big changes. The quilt
> format is probably easier for someone wishing to work on it anyway.
Hmm, we still left out some exports...
--Mark
--
Mark Fasheh
Senior Software Developer, Oracle
mark.fasheh@oracle.com
From: Mark Fasheh <mark.fasheh@oracle.com>
[PATCH] Export simple_write_begin, simple_write_end
These are used by configfs, which can be built as a module.
Signed-off-by: Mark Fasheh <mark.fasheh@oracle.com>
---
fs/libfs.c | 2 ++
1 files changed, 2 insertions(+), 0 deletions(-)
36f5d6a135c9f3f30fee3d0e4ffa887e1803ac95
diff --git a/fs/libfs.c b/fs/libfs.c
index d687819..51f9748 100644
--- a/fs/libfs.c
+++ b/fs/libfs.c
@@ -656,6 +656,8 @@ EXPORT_SYMBOL(dcache_dir_open);
EXPORT_SYMBOL(dcache_readdir);
EXPORT_SYMBOL(generic_read_dir);
EXPORT_SYMBOL(get_sb_pseudo);
+EXPORT_SYMBOL(simple_write_begin);
+EXPORT_SYMBOL(simple_write_end);
EXPORT_SYMBOL(simple_commit_write);
EXPORT_SYMBOL(simple_dir_inode_operations);
EXPORT_SYMBOL(simple_dir_operations);
--
1.3.3
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
WARNING: multiple messages have this Message-ID (diff)
From: Mark Fasheh <mark.fasheh@oracle.com>
To: Nick Piggin <npiggin@suse.de>
Cc: Linux Filesystems <linux-fsdevel@vger.kernel.org>,
reiserfs-list@namesys.com, linux-ext4@vger.kernel.org,
xfs@oss.sgi.com, nfs@lists.sourceforge.net,
cluster-devel@redhat.com, jfs-discussion@lists.sourceforge.net
Subject: Re: Announce: new-aops-1 for 2.6.21-rc3
Date: Thu, 15 Mar 2007 12:53:51 -0700 [thread overview]
Message-ID: <20070315195351.GE21942@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.
>
> At 15 patches (including the initial buffered write deadlock fixes),
> it is too much to keep posting -- not much has fundamentally changed,
> so I'll just post occasionally if we make big changes. The quilt
> format is probably easier for someone wishing to work on it anyway.
Hmm, we still left out some exports...
--Mark
--
Mark Fasheh
Senior Software Developer, Oracle
mark.fasheh@oracle.com
From: Mark Fasheh <mark.fasheh@oracle.com>
[PATCH] Export simple_write_begin, simple_write_end
These are used by configfs, which can be built as a module.
Signed-off-by: Mark Fasheh <mark.fasheh@oracle.com>
---
fs/libfs.c | 2 ++
1 files changed, 2 insertions(+), 0 deletions(-)
36f5d6a135c9f3f30fee3d0e4ffa887e1803ac95
diff --git a/fs/libfs.c b/fs/libfs.c
index d687819..51f9748 100644
--- a/fs/libfs.c
+++ b/fs/libfs.c
@@ -656,6 +656,8 @@ EXPORT_SYMBOL(dcache_dir_open);
EXPORT_SYMBOL(dcache_readdir);
EXPORT_SYMBOL(generic_read_dir);
EXPORT_SYMBOL(get_sb_pseudo);
+EXPORT_SYMBOL(simple_write_begin);
+EXPORT_SYMBOL(simple_write_end);
EXPORT_SYMBOL(simple_commit_write);
EXPORT_SYMBOL(simple_dir_inode_operations);
EXPORT_SYMBOL(simple_dir_operations);
--
1.3.3
next prev parent reply other threads:[~2007-03-15 19:53 UTC|newest]
Thread overview: 24+ 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 16:17 ` [Cluster-devel] " Nick Piggin
2007-03-15 19:32 ` [Cluster-devel] " Joel Becker
2007-03-15 19:32 ` Joel Becker
2007-03-15 19:32 ` Joel Becker
2007-03-15 19:57 ` [Cluster-devel] " Nick Piggin
2007-03-15 19:57 ` Nick Piggin
2007-03-15 19:53 ` Mark Fasheh [this message]
2007-03-15 19:53 ` Mark Fasheh
2007-03-15 19:53 ` Mark Fasheh
2007-03-15 19:57 ` [Cluster-devel] " Nick Piggin
2007-03-15 19:57 ` Nick Piggin
2007-03-15 19:57 ` Nick Piggin
2007-03-15 21:08 ` [Cluster-devel] " Mark Fasheh
2007-03-15 21:08 ` Mark Fasheh
2007-03-15 21:08 ` Mark Fasheh
2007-03-15 23:47 ` [Cluster-devel] " Mark Fasheh
2007-03-15 23:47 ` Mark Fasheh
2007-03-15 23:47 ` Mark Fasheh
2007-03-20 5:36 ` [Cluster-devel] " Nick Piggin
2007-03-20 5:36 ` Nick Piggin
2007-04-01 5:42 ` Nick Piggin
2007-04-02 2:14 ` 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=20070315195351.GE21942@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 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.