From: Chao Yu <yuchao0@huawei.com>
To: sunqiuyang <sunqiuyang@huawei.com>,
<linux-kernel@vger.kernel.org>, <linux-fsdevel@vger.kernel.org>,
<linux-f2fs-devel@lists.sourceforge.net>
Cc: <fangwei1@huawei.com>, <yuchangchun1@huawei.com>
Subject: Re: [PATCH] f2fs: fix block address for __check_sit_bitmap
Date: Tue, 18 Dec 2018 18:36:15 +0800 [thread overview]
Message-ID: <cbfb1b04-34bd-951b-089d-1561e3746d46@huawei.com> (raw)
In-Reply-To: <20181218093223.25242-1-sunqiuyang@huawei.com>
On 2018/12/18 17:32, sunqiuyang wrote:
> From: Qiuyang Sun <sunqiuyang@huawei.com>
>
> Should use lstart (logical start address) instead of start (in dev) here.
> This fixes a bug in multi-device scenarios.
Good catch!
>
> Signed-off-by: Qiuyang Sun <sunqiuyang@huawei.com>
Reviewed-by: Chao Yu <yuchao0@huawei.com>
Thanks,
prev parent reply other threads:[~2018-12-18 10:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-18 9:32 [PATCH] f2fs: fix block address for __check_sit_bitmap sunqiuyang
2018-12-18 10:36 ` 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=cbfb1b04-34bd-951b-089d-1561e3746d46@huawei.com \
--to=yuchao0@huawei.com \
--cc=fangwei1@huawei.com \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sunqiuyang@huawei.com \
--cc=yuchangchun1@huawei.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;
as well as URLs for NNTP newsgroup(s).