Linux Btrfs filesystem development
 help / color / mirror / Atom feed
From: "Liu Hui" <onlyflyer@gmail.com>
To: "Yan Zheng" <yanzheng@21cn.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: [PATH]Fix cow semantic in run_delalloc_nocow()
Date: Thu, 20 Nov 2008 21:47:05 +0800	[thread overview]
Message-ID: <2c3b11250811200547x4902686cicf1d7604d101275d@mail.gmail.com> (raw)
In-Reply-To: <3d0408630811200530h254ad68ej75df9f6b73745a40@mail.gmail.com>

Ok, this is the new patch.

-- 
Thanks & Best Regards
Liu Hui
--

diff --git a/inode.c b/inode.c
index 2c77e09..5e3789f 100644
--- a/inode.c
+++ b/inode.c
@@ -1114,10 +1114,10 @@ static int run_delalloc_range(struct inode
*inode, struct page *locked_page,
        if (btrfs_test_opt(root, NODATACOW) ||
            btrfs_test_flag(inode, NODATACOW))
                ret = run_delalloc_nocow(inode, locked_page, start, end,
-                                        page_started, 0, nr_written);
+                                        page_started, 1, nr_written);
        else if (btrfs_test_flag(inode, PREALLOC))
                ret = run_delalloc_nocow(inode, locked_page, start, end,
-                                        page_started, 1, nr_written);
+                                        page_started, 0, nr_written);
        else
                ret = cow_file_range_async(inode, locked_page, start, end,
                                     page_started, nr_written);

  reply	other threads:[~2008-11-20 13:47 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-20  9:02 [PATH]Fix cow semantic in run_delalloc_nocow() Liu Hui
2008-11-20 13:30 ` Yan Zheng
2008-11-20 13:47   ` Liu Hui [this message]
2008-11-20 16:19     ` Chris Mason
2008-11-21  4:47       ` [PATCH]Fix " Liu Hui
2008-11-21 12:14         ` Chris Mason

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=2c3b11250811200547x4902686cicf1d7604d101275d@mail.gmail.com \
    --to=onlyflyer@gmail.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=yanzheng@21cn.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