From: Chao Yu <yuchao0@huawei.com>
To: Jaegeuk Kim <jaegeuk@kernel.org>
Cc: linux-kernel@vger.kernel.org, linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [f2fs-dev] [PATCH 2/4] f2fs: compress: revert error path fix
Date: Wed, 8 Jan 2020 17:33:40 +0800 [thread overview]
Message-ID: <d2d21997-42f2-217a-a4cb-66b7fe8ef3e8@huawei.com> (raw)
In-Reply-To: <20200106192631.GF50058@jaegeuk-macbookpro.roam.corp.google.com>
On 2020/1/7 3:26, Jaegeuk Kim wrote:
> Hi Chao,
>
> Could you please check this out?
> https://github.com/jaegeuk/f2fs/commits/g-dev-test
Looks good to me, I add some minor comments on github.
Any comments on below thread?
Re: [f2fs-dev] [PATCH 3/4] f2fs: compress: fix error path in prepare_compress_overwrite()
Thanks,
>
> Thanks,
>
> On 01/06, Chao Yu wrote:
>> Revert incorrect fix in ("TEMP: f2fs: support data compression - fix1")
>>
>> Signed-off-by: Chao Yu <yuchao0@huawei.com>
>> ---
>> fs/f2fs/compress.c | 6 +++---
>> 1 file changed, 3 insertions(+), 3 deletions(-)
>>
>> diff --git a/fs/f2fs/compress.c b/fs/f2fs/compress.c
>> index f993b4ce1970..fc4510729654 100644
>> --- a/fs/f2fs/compress.c
>> +++ b/fs/f2fs/compress.c
>> @@ -601,7 +601,7 @@ static int prepare_compress_overwrite(struct compress_ctx *cc,
>> fgp_flag, GFP_NOFS);
>> if (!page) {
>> ret = -ENOMEM;
>> - goto release_pages;
>> + goto unlock_pages;
>> }
>>
>> if (PageUptodate(page))
>> @@ -616,13 +616,13 @@ static int prepare_compress_overwrite(struct compress_ctx *cc,
>> ret = f2fs_read_multi_pages(cc, &bio, cc->cluster_size,
>> &last_block_in_bio, false);
>> if (ret)
>> - goto unlock_pages;
>> + goto release_pages;
>> if (bio)
>> f2fs_submit_bio(sbi, bio, DATA);
>>
>> ret = f2fs_init_compress_ctx(cc);
>> if (ret)
>> - goto unlock_pages;
>> + goto release_pages;
>> }
>>
>> for (i = 0; i < cc->cluster_size; i++) {
>> --
>> 2.18.0.rc1
> .
>
_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
next prev parent reply other threads:[~2020-01-08 9:34 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-06 8:01 [f2fs-dev] [PATCH 1/4] f2fs: compress: fix panic in mkwrite Chao Yu
2020-01-06 8:01 ` [f2fs-dev] [PATCH 2/4] f2fs: compress: revert error path fix Chao Yu
2020-01-06 19:26 ` Jaegeuk Kim
2020-01-08 9:33 ` Chao Yu [this message]
2020-01-06 8:01 ` [f2fs-dev] [PATCH 3/4] f2fs: compress: fix error path in prepare_compress_overwrite() Chao Yu
2020-01-06 19:08 ` Jaegeuk Kim
2020-01-07 1:35 ` Chao Yu
2020-01-08 20:49 ` Jaegeuk Kim
2020-01-06 8:01 ` [f2fs-dev] [PATCH 4/4] f2fs: compress: release compress context in caller of f2fs_read_multi_pages() Chao Yu
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=d2d21997-42f2-217a-a4cb-66b7fe8ef3e8@huawei.com \
--to=yuchao0@huawei.com \
--cc=jaegeuk@kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).