From: Chao Yu <yuchao0@huawei.com>
To: Jaegeuk Kim <jaegeuk@kernel.org>, <linux-kernel@vger.kernel.org>,
<linux-f2fs-devel@lists.sourceforge.net>
Subject: Re: [f2fs-dev] [PATCH 2/4] f2fs: don't put new_page twice in f2fs_rename
Date: Sat, 28 Dec 2019 14:50:48 +0800 [thread overview]
Message-ID: <049ce80a-d977-d15a-ad56-11ad7f5edd1f@huawei.com> (raw)
In-Reply-To: <20191218200947.20445-2-jaegeuk@kernel.org>
On 2019/12/19 4:09, Jaegeuk Kim wrote:
> In f2fs_rename(), new_page is gone after f2fs_set_link(), but it tries
> to put again when whiteout is failed and jumped to put_out_dir.
>
> Signed-off-by: Jaegeuk Kim <jaegeuk@kernel.org>
Reviewed-by: Chao Yu <yuchao0@huawei.com>
Thanks,
next prev parent reply other threads:[~2019-12-28 6:50 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-18 20:09 [PATCH 1/4] f2fs: convert inline_dir early before starting rename Jaegeuk Kim
2019-12-18 20:09 ` [PATCH 2/4] f2fs: don't put new_page twice in f2fs_rename Jaegeuk Kim
2019-12-28 6:50 ` Chao Yu [this message]
2019-12-18 20:09 ` [PATCH 3/4] f2fs: declare nested quota_sem and remove unnecessary sems Jaegeuk Kim
2019-12-18 20:09 ` [PATCH 4/4] f2fs: free sysfs kobject Jaegeuk Kim
2019-12-28 10:09 ` [f2fs-dev] " Chao Yu
2019-12-28 6:32 ` [f2fs-dev] [PATCH 1/4] f2fs: convert inline_dir early before starting rename Chao Yu
2019-12-31 0:06 ` Jaegeuk Kim
2019-12-31 1:22 ` Chao Yu
2020-01-02 18:36 ` [PATCH 1/4 v2] " Jaegeuk Kim
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=049ce80a-d977-d15a-ad56-11ad7f5edd1f@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).