From: Tao Ma <tao.ma@oracle.com>
To: ocfs2-devel@oss.oracle.com
Subject: [Ocfs2-devel] [PATCH v2] ocfs2: Don't duplicate page passes i_size during CoW.
Date: Tue, 13 Jul 2010 22:25:53 +0800 [thread overview]
Message-ID: <4C3C7771.5000103@oracle.com> (raw)
In-Reply-To: <20100713081538.GC31479@mail.oracle.com>
Joel Becker wrote:
> On Tue, Jul 13, 2010 at 01:13:06AM -0700, Joel Becker wrote:
>
>> On Tue, Jul 13, 2010 at 11:22:32AM +0800, Tao Ma wrote:
>>
>>> + /*
>>> + * We only duplicate pages until we reach i_size.
>>> + * So trim 'end' to the boundary of that page.
>>> + */
>>> + if (end > i_size_read(context->inode))
>>> + end = ((i_size_read(context->inode) + PAGE_CACHE_SIZE - 1) >>
>>> + PAGE_CACHE_SHIFT) << PAGE_CACHE_SHIFT;
>>>
>
> Why even worry about that? We only need up to i_size. If end
> is safe and not page aligned, so is i_size.
>
i_size isn't safe in ocfs2_duplicate_clusters_by_page. Check the below
function.
if (page_has_buffers(page)) {
ret = walk_page_buffers(handle, page_buffers(page),
from, to, &partial,
ocfs2_clear_cow_buffer);
if (ret) {
mlog_errno(ret);
goto unlock;
}
}
So 'to' is limited to 'map_end' and then 'end'. If we set 'end' to
i_size, we may not clear all the buffer heads
since walk_page_buffers will only call ocfs2_clear_cow_buffer within
from and to.
Maybe we can improve it somehow later, but I would leave it as-is now.
Regards,
Tao
next prev parent reply other threads:[~2010-07-13 14:25 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-12 7:19 [Ocfs2-devel] [PATCH] ocfs2: Don't duplicate page passes i_size during CoW Tao Ma
2010-07-12 9:14 ` Joel Becker
2010-07-13 3:22 ` [Ocfs2-devel] [PATCH v2] " Tao Ma
2010-07-13 8:13 ` Joel Becker
2010-07-13 8:15 ` Joel Becker
2010-07-13 14:25 ` Tao Ma [this message]
2010-07-13 18:38 ` Joel Becker
2010-07-14 0:29 ` Tao Ma
2010-07-14 3:19 ` [Ocfs2-devel] [PATCH v5] " Tao Ma
2010-07-15 1:15 ` tristan
2010-07-15 21:02 ` Joel Becker
2010-07-13 14:50 ` [Ocfs2-devel] [PATCH v3] " Tao Ma
2010-07-13 15:30 ` [Ocfs2-devel] [PATCH v4] " Tao Ma
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=4C3C7771.5000103@oracle.com \
--to=tao.ma@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.