From: Mark Fasheh <mark.fasheh@oracle.com>
To: ocfs2-devel@oss.oracle.com
Subject: [Ocfs2-devel] [PATCH 0/3] Properly protect the extent map
Date: Mon Apr 2 11:47:15 2007 [thread overview]
Message-ID: <20070402184713.GB21982@ca-server1.us.oracle.com> (raw)
In-Reply-To: <20070329005041.518030000@oracle.com>
On Wed, Mar 28, 2007 at 06:27:07PM -0700, Joel Becker wrote:
> The patches that follow are against mainline. They have been tested
> against 1.2 with local mounts.
>
> Patches (1) and (2) will be ported to the ocfs2 1.2 branch directly,
> and all three fixes will be pushed to mainline.
Ok. These patches look good - thanks. Have you had a chance to test against
mainline?
--Mark
--
Mark Fasheh
Senior Software Developer, Oracle
mark.fasheh@oracle.com
next prev parent reply other threads:[~2007-04-02 11:47 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-28 18:50 [Ocfs2-devel] [PATCH 0/3] Properly protect the extent map Joel Becker
2007-03-28 18:50 ` [Ocfs2-devel] [PATCH 1/3] ocfs2: Wrap access of directory allocations with ip_alloc_sem Joel Becker
2007-03-28 18:51 ` [Ocfs2-devel] [PATCH 2/3] ocfs2: Properly lock extent map size changes Joel Becker
2007-03-28 18:51 ` [Ocfs2-devel] [PATCH 3/3] ocfs2: Local mounts should not truncate the extent map Joel Becker
2007-03-29 2:04 ` [Ocfs2-devel] [PATCH 0/3] Properly protect " Fabio Massimo Di Nitto
2007-03-29 9:41 ` Sunil Mushran
2007-04-02 11:45 ` Mark Fasheh
2007-04-02 11:48 ` Fabio Massimo Di Nitto
2007-04-02 11:58 ` Mark Fasheh
2007-04-02 12:00 ` Fabio Massimo Di Nitto
2007-04-02 11:47 ` Mark Fasheh [this message]
2007-04-02 16:55 ` Joel Becker
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=20070402184713.GB21982@ca-server1.us.oracle.com \
--to=mark.fasheh@oracle.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.