The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Chao Yu <yuchao0@huawei.com>
To: Daeho Jeong <daeho43@gmail.com>, <linux-kernel@vger.kernel.org>,
	<linux-f2fs-devel@lists.sourceforge.net>,
	<kernel-team@android.com>
Cc: Daeho Jeong <daehojeong@google.com>
Subject: Re: [f2fs-dev] [PATCH] f2fs: prevent compressed file from being disabled after releasing cblocks
Date: Mon, 31 Aug 2020 14:22:52 +0800	[thread overview]
Message-ID: <a3efc099-3426-310b-720e-8ae5d509e68a@huawei.com> (raw)
In-Reply-To: <20200828054629.583577-1-daeho43@gmail.com>

On 2020/8/28 13:46, Daeho Jeong wrote:
> From: Daeho Jeong <daehojeong@google.com>
> 
> After releasing cblocks, the compressed file can be accidentally
> disabled in compression mode, since it has zero cblocks. As we are
> using IMMUTABLE flag to present released cblocks state, we can add
> IMMUTABLE state check when considering the compressed file disabling.
> 
> Signed-off-by: Daeho Jeong <daehojeong@google.com>

Reviewed-by: Chao Yu <yuchao0@huawei.com>

Thanks,

      parent reply	other threads:[~2020-08-31  6:23 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-28  5:46 [PATCH] f2fs: prevent compressed file from being disabled after releasing cblocks Daeho Jeong
2020-08-30  3:23 ` [f2fs-dev] " Chao Yu
2020-08-30 23:42   ` Daeho Jeong
2020-08-31  1:24     ` Chao Yu
2020-08-31  1:44       ` Daeho Jeong
2020-08-31  2:31         ` Chao Yu
2020-08-31  3:55           ` Daeho Jeong
2020-08-31  6:06             ` Chao Yu
2020-08-31  6:15               ` Daeho Jeong
2020-08-31  6:22 ` Chao Yu [this message]

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=a3efc099-3426-310b-720e-8ae5d509e68a@huawei.com \
    --to=yuchao0@huawei.com \
    --cc=daeho43@gmail.com \
    --cc=daehojeong@google.com \
    --cc=kernel-team@android.com \
    --cc=linux-f2fs-devel@lists.sourceforge.net \
    --cc=linux-kernel@vger.kernel.org \
    /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