From: Chao Yu <yuchao0@huawei.com>
To: Markus Elfring <Markus.Elfring@web.de>,
<linux-f2fs-devel@lists.sourceforge.net>
Cc: Jaegeuk Kim <jaegeuk@kernel.org>, linux-kernel@vger.kernel.org
Subject: Re: [f2fs-dev] [PATCH] f2fs: fix to avoid page count leak
Date: Mon, 13 Apr 2020 08:34:40 +0800 [thread overview]
Message-ID: <d228c74b-0d33-e22c-56c8-f2bfd691c985@huawei.com> (raw)
In-Reply-To: <c50f4bff-1c14-931d-ee07-a2f5dc336785@web.de>
On 2020/4/11 3:19, Markus Elfring wrote:
>> In below error path, we missed to release reference count of pages
>> in compressed cluster, fix it.
>> - f2fs_mpage_readpages()
>> - f2fs_read_multi_pages()
>
> I suggest to improve the commit message.
>
> Would you like to add the tag “Fixes” to the change description?
Sure, will update in v2, thanks.
Thanks,
>
> Regards,
> Markus
> .
>
_______________________________________________
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-04-13 0:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-10 19:19 [f2fs-dev] [PATCH] f2fs: fix to avoid page count leak Markus Elfring
2020-04-13 0:34 ` Chao Yu [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-04-10 8:51 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=d228c74b-0d33-e22c-56c8-f2bfd691c985@huawei.com \
--to=yuchao0@huawei.com \
--cc=Markus.Elfring@web.de \
--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).