From: "Matias Bjørling" <mb@lightnvm.io>
To: axboe@kernel.dk
Cc: hans.ml.holmberg@owltronix.com, linux-block@vger.kernel.org,
linux-kernel@vger.kernel.org, javier@cnexlabs.com,
hans.holmberg@cnexlabs.com
Subject: Re: [PATCH] lightnvm: pblk: assume that chunks are closed on 1.2 devices
Date: Tue, 26 Jun 2018 14:10:34 +0200 [thread overview]
Message-ID: <3d09296d-ace3-f025-b6d9-5d99ce6b9fc8@lightnvm.io> (raw)
In-Reply-To: <1529399189-3239-1-git-send-email-hans.ml.holmberg@owltronix.com>
On 06/19/2018 11:06 AM, Hans Holmberg wrote:
> From: Hans Holmberg <hans.holmberg@cnexlabs.com>
>
> We can't know if a block is closed or not on 1.2 devices, so assume
> closed state to make sure that blocks are erased before writing.
>
> Fixes: 32ef9412c114 ("lightnvm: pblk: implement get log report chunk")
>
> Signed-off-by: Hans Holmberg <hans.holmberg@cnexlabs.com>
> ---
>
> This patch applies on:
> ssh://github.com/OpenChannelSSD/linux branch for-4.19/core
>
> drivers/lightnvm/pblk-init.c | 5 +++--
> 1 file changed, 3 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/lightnvm/pblk-init.c b/drivers/lightnvm/pblk-init.c
> index aa24264..3b8aa4a 100644
> --- a/drivers/lightnvm/pblk-init.c
> +++ b/drivers/lightnvm/pblk-init.c
> @@ -717,10 +717,11 @@ static int pblk_setup_line_meta_12(struct pblk *pblk, struct pblk_line *line,
>
> /*
> * In 1.2 spec. chunk state is not persisted by the device. Thus
> - * some of the values are reset each time pblk is instantiated.
> + * some of the values are reset each time pblk is instantiated,
> + * so we have to assume that the block is closed.
> */
> if (lun_bb_meta[line->id] == NVM_BLK_T_FREE)
> - chunk->state = NVM_CHK_ST_FREE;
> + chunk->state = NVM_CHK_ST_CLOSED;
> else
> chunk->state = NVM_CHK_ST_OFFLINE;
>
>
Hi Jens,
Would it be possible to pick this patch up for 4.18? It is a temporary
fix that lets pblk continue to work with 1.2 OCSSD drives that has open
blocks on initialization. Without it, writes will fail, as pblk assumes
that the blocks are free.
A proper fix that scans the block state on initialization will be ready
for 4.19.
Thank you,
Matias
prev parent reply other threads:[~2018-06-26 12:10 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-19 9:06 Hans Holmberg
2018-06-26 8:41 ` Matias Bjørling
2018-06-26 9:37 ` Javier Gonzalez
2018-06-26 10:38 ` Matias Bjørling
2018-06-26 11:31 ` Hans Holmberg
2018-06-26 11:44 ` Matias Bjørling
2018-06-26 11:54 ` Javier Gonzalez
2018-06-26 12:13 ` Matias Bjørling
2018-06-26 12:26 ` Javier González
2018-06-26 12:10 ` Matias Bjørling [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=3d09296d-ace3-f025-b6d9-5d99ce6b9fc8@lightnvm.io \
--to=mb@lightnvm.io \
--cc=axboe@kernel.dk \
--cc=hans.holmberg@cnexlabs.com \
--cc=hans.ml.holmberg@owltronix.com \
--cc=javier@cnexlabs.com \
--cc=linux-block@vger.kernel.org \
--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
all inboxes | Powered by JetHome®