From: Junxiao Bi <junxiao.bi@oracle.com>
To: ocfs2-devel@oss.oracle.com
Subject: [Ocfs2-devel] [PATCH 3/4] ocfs2: fix disk file size and memory file size mismatch
Date: Tue, 1 Dec 2015 14:44:54 +0800 [thread overview]
Message-ID: <565D41E6.9040706@oracle.com> (raw)
In-Reply-To: <1448007799-10914-3-git-send-email-ryan.ding@oracle.com>
On 11/20/2015 04:23 PM, Ryan Ding wrote:
> When doing append direct write in an already allocated cluster, and fast path
> in ocfs2_dio_get_block() is triggered, function ocfs2_dio_end_io_write() will
> be skipped as there is no context allocated. So disk file size will not be
> changed as it should be.
> The solution is to skip fast path when we are about to change file size.
>
> Fixes: af1310367f41 ("ocfs2: fix sparse file & data ordering issue in direct io.")
Patch looks good. But this tag is useless for a commit not merged into
mainline. Maybe we can fold this patch into above commit.
Thanks,
Junxiao.
> Signed-off-by: Ryan Ding <ryan.ding@oracle.com>
> ---
> fs/ocfs2/aops.c | 27 +++++++++++++++++----------
> 1 files changed, 17 insertions(+), 10 deletions(-)
>
> diff --git a/fs/ocfs2/aops.c b/fs/ocfs2/aops.c
> index d571509..f33cfe4 100644
> --- a/fs/ocfs2/aops.c
> +++ b/fs/ocfs2/aops.c
> @@ -2167,19 +2167,26 @@ static int ocfs2_dio_get_block(struct inode *inode, sector_t iblock,
> mlog(0, "get block of %lu at %llu:%u req %u\n",
> inode->i_ino, pos, len, total_len);
>
> - down_read(&oi->ip_alloc_sem);
> - /* This is the fast path for re-write. */
> - ret = ocfs2_get_block(inode, iblock, bh_result, create);
> + /*
> + * Because we need to change file size in ocfs2_dio_end_io_write(), or
> + * we may need to add it to orphan dir. So can not fall to fast path
> + * while file size will be changed.
> + */
> + if (pos + total_len <= i_size_read(inode)) {
> + down_read(&oi->ip_alloc_sem);
> + /* This is the fast path for re-write. */
> + ret = ocfs2_get_block(inode, iblock, bh_result, create);
>
> - up_read(&oi->ip_alloc_sem);
> + up_read(&oi->ip_alloc_sem);
>
> - if (buffer_mapped(bh_result) &&
> - !buffer_new(bh_result) &&
> - ret == 0)
> - goto out;
> + if (buffer_mapped(bh_result) &&
> + !buffer_new(bh_result) &&
> + ret == 0)
> + goto out;
>
> - /* Clear state set by ocfs2_get_block. */
> - bh_result->b_state = 0;
> + /* Clear state set by ocfs2_get_block. */
> + bh_result->b_state = 0;
> + }
>
> dwc = ocfs2_dio_alloc_write_ctx(bh_result, &first_get_block);
> if (unlikely(dwc == NULL)) {
>
next prev parent reply other threads:[~2015-12-01 6:44 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-20 8:23 [Ocfs2-devel] [PATCH 1/4] ocfs2: fix ip_unaligned_aio deadlock with dio work queue Ryan Ding
2015-11-20 8:23 ` [Ocfs2-devel] [PATCH 2/4] ocfs2: take ip_alloc_sem in ocfs2_dio_get_block & ocfs2_dio_end_io_write Ryan Ding
2015-12-01 6:36 ` Junxiao Bi
2015-11-20 8:23 ` [Ocfs2-devel] [PATCH 3/4] ocfs2: fix disk file size and memory file size mismatch Ryan Ding
2015-12-01 6:44 ` Junxiao Bi [this message]
2015-11-20 8:23 ` [Ocfs2-devel] [PATCH 4/4] ocfs2: Fix a deadlock issue in ocfs2_dio_end_io_write() Ryan Ding
2015-12-01 6:53 ` Junxiao Bi
2015-11-24 0:26 ` [Ocfs2-devel] [PATCH 1/4] ocfs2: fix ip_unaligned_aio deadlock with dio work queue Andrew Morton
2015-11-24 3:24 ` Ryan Ding
2015-12-01 4:42 ` Junxiao Bi
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=565D41E6.9040706@oracle.com \
--to=junxiao.bi@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox