From: Javier Gonzalez <javier@cnexlabs.com>
To: "Matias Bjørling" <mb@lightnvm.io>
Cc: Heiner Litz <hlitz@ucsc.edu>,
"linux-block@vger.kernel.org" <linux-block@vger.kernel.org>,
"matias@lightnvm.io" <matias@lightnvm.io>
Subject: Re: [PATCH] lightnvm: fix bad block initialization
Date: Sat, 24 Feb 2018 09:11:51 +0000 [thread overview]
Message-ID: <90B573AB-6969-4159-9DCF-62EC47022AD1@cnexlabs.com> (raw)
In-Reply-To: <02770a13-9699-aa8d-bcf2-c7aaefe28623@lightnvm.io>
[-- Attachment #1: Type: text/plain, Size: 1390 bytes --]
> On 23 Feb 2018, at 19.45, Matias Bjørling <mb@lightnvm.io> wrote:
>
> On 02/23/2018 06:40 PM, Heiner Litz wrote:
>> fix reading bad block device information to correctly setup the per line
>> blk_bitmap during lightnvm initialization
>>
>> Signed-off-by: Heiner Litz <hlitz@ucsc.edu>
>> ---
>> drivers/lightnvm/pblk-init.c | 3 ++-
>> 1 file changed, 2 insertions(+), 1 deletion(-)
>>
>> diff --git a/drivers/lightnvm/pblk-init.c b/drivers/lightnvm/pblk-init.c
>> index 86a94a7faa96..e0eba150ac7e 100644
>> --- a/drivers/lightnvm/pblk-init.c
>> +++ b/drivers/lightnvm/pblk-init.c
>> @@ -461,10 +461,11 @@ static int pblk_bb_line(struct pblk *pblk, struct pblk_line *line,
>> struct nvm_tgt_dev *dev = pblk->dev;
>> struct nvm_geo *geo = &dev->geo;
>> int i, bb_cnt = 0;
>> + int blk_per_lun = geo->nr_chks * geo->plane_mode;
>>
>> for (i = 0; i < blk_per_line; i++) {
>> struct pblk_lun *rlun = &pblk->luns[i];
>> - u8 *lun_bb_log = bb_log + i * blk_per_line;
>> + u8 *lun_bb_log = bb_log + i * blk_per_lun;
>>
>> if (lun_bb_log[line->id] == NVM_BLK_T_FREE)
>> continue;
>
> Thanks Heiner. Applied.
The patch looks good, but it is missing:
Fixes: 36b3b712e81dc ("lightnvm: pblk: refactor bad block identification")
Matias, please add this when picking up.
Reviewed-by: Javier González <javier@cnexlabs.com>
[-- Attachment #2: Message signed with OpenPGP --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2018-02-24 9:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-23 17:40 [PATCH] lightnvm: fix bad block initialization Heiner Litz
2018-02-23 18:45 ` Matias Bjørling
2018-02-24 9:11 ` Javier Gonzalez [this message]
2018-02-24 9:15 ` Javier Gonzalez
-- strict thread matches above, loose matches on Subject: below --
2018-02-22 8:10 Heiner Litz
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=90B573AB-6969-4159-9DCF-62EC47022AD1@cnexlabs.com \
--to=javier@cnexlabs.com \
--cc=hlitz@ucsc.edu \
--cc=linux-block@vger.kernel.org \
--cc=matias@lightnvm.io \
--cc=mb@lightnvm.io \
/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