From: Joel Becker <Joel.Becker@oracle.com>
To: ocfs2-devel@oss.oracle.com
Subject: [Ocfs2-devel] [PATCH 1/1] ocfs2: Initialize the cluster we're writing to in a non-sparse extend
Date: Fri, 7 Aug 2009 13:19:34 -0700 [thread overview]
Message-ID: <20090807201934.GD30923@mail.oracle.com> (raw)
In-Reply-To: <1249600378-18706-2-git-send-email-sunil.mushran@oracle.com>
On Thu, Aug 06, 2009 at 04:12:58PM -0700, Sunil Mushran wrote:
> In a non-sparse extend, we correctly allocate (and zero) the clusters between
> the old_i_size and pos, but we don't zero the portions of the cluster we're
> writing to outside of pos<->len.
>
> It handles clustersize > pagesize and blocksize < pagesize.
>
> [Cleaned up by Joel Becker.]
>
> Signed-off-by: Sunil Mushran <sunil.mushran@oracle.com>
This is now in the fixes branch of ocfs2.git.
Joel
--
"Born under a bad sign.
I been down since I began to crawl.
If it wasn't for bad luck,
I wouldn't have no luck at all."
Joel Becker
Principal Software Developer
Oracle
E-mail: joel.becker at oracle.com
Phone: (650) 506-8127
next prev parent reply other threads:[~2009-08-07 20:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-06 23:12 [Ocfs2-devel] Non-sparse write fix -v4 Sunil Mushran
2009-08-06 23:12 ` [Ocfs2-devel] [PATCH 1/1] ocfs2: Initialize the cluster we're writing to in a non-sparse extend Sunil Mushran
2009-08-07 20:19 ` Joel Becker [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-08-03 18:13 [Ocfs2-devel] Non sparse init fix v3 Sunil Mushran
2009-08-03 18:13 ` [Ocfs2-devel] [PATCH 1/1] ocfs2: Initialize the cluster we're writing to in a non-sparse extend Sunil Mushran
2009-08-03 21:15 ` Mark Fasheh
2009-08-02 20:04 [Ocfs2-devel] Non sparse extend init issue Sunil Mushran
2009-08-02 20:04 ` [Ocfs2-devel] [PATCH 1/1] ocfs2: Initialize the cluster we're writing to in a non-sparse extend Sunil Mushran
2009-08-02 22:05 ` 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=20090807201934.GD30923@mail.oracle.com \
--to=joel.becker@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.