From: Greg KH <gregkh@linuxfoundation.org>
To: Xiaoming Ni <nixiaoming@huawei.com>
Cc: wangle6@huawei.com, vigneshr@ti.com, richard@nod.at,
houtao1@huawei.com, linux-kernel@vger.kernel.org,
linux-mtd@lists.infradead.org, zhangweimin12@huawei.com,
miquel.raynal@bootlin.com, yebin10@huawei.com
Subject: Re: [PATCH v4] mtd: clear cache_state to avoid writing to bad blocks repeatedly
Date: Tue, 31 Mar 2020 12:05:26 +0200 [thread overview]
Message-ID: <20200331100526.GC1204199@kroah.com> (raw)
In-Reply-To: <1585618319-119741-1-git-send-email-nixiaoming@huawei.com>
On Tue, Mar 31, 2020 at 09:31:59AM +0800, Xiaoming Ni wrote:
> The function call process is as follows:
> mtd_blktrans_work()
> while (1)
> do_blktrans_request()
> mtdblock_writesect()
> do_cached_write()
> write_cached_data() /*if cache_state is STATE_DIRTY*/
> erase_write()
>
> write_cached_data() returns failure without modifying cache_state
> and cache_offset. So when do_cached_write() is called again,
> write_cached_data() will be called again to perform erase_write()
> on the same cache_offset.
>
> But if this cache_offset points to a bad block, erase_write() will
> always return -EIO. Writing to this mtdblk is equivalent to losing
> the current data, and repeatedly writing to the bad block.
>
> Repeatedly writing a bad block has no real benefits,
> but brings some negative effects:
> 1 Lost subsequent data
> 2 Loss of flash device life
> 3 erase_write() bad blocks are very time-consuming. For example:
> the function do_erase_oneblock() in chips/cfi_cmdset_0020.c or
> chips/cfi_cmdset_0002.c may take more than 20 seconds to return
>
> Therefore, when erase_write() returns -EIO in write_cached_data(),
> clear cache_state to avoid writing to bad blocks repeatedly.
>
> Signed-off-by: Xiaoming Ni <nixiaoming@huawei.com>
> Reviewed-by: Miquel Raynal <miquel.raynal@bootlin.com>
> ---
> drivers/mtd/mtdblock.c | 11 +++++++----
> 1 file changed, 7 insertions(+), 4 deletions(-)
$ ./scripts/get_maintainer.pl --file drivers/mtd/mtdblock.c
Miquel Raynal <miquel.raynal@bootlin.com> (maintainer:MEMORY TECHNOLOGY DEVICES (MTD))
Richard Weinberger <richard@nod.at> (maintainer:MEMORY TECHNOLOGY DEVICES (MTD))
Vignesh Raghavendra <vigneshr@ti.com> (maintainer:MEMORY TECHNOLOGY DEVICES (MTD))
linux-mtd@lists.infradead.org (open list:MEMORY TECHNOLOGY DEVICES (MTD))
linux-kernel@vger.kernel.org (open list)
No where on there is my name/email, so why am I getting these?
confused,
greg k-h
______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/
WARNING: multiple messages have this Message-ID (diff)
From: Greg KH <gregkh@linuxfoundation.org>
To: Xiaoming Ni <nixiaoming@huawei.com>
Cc: miquel.raynal@bootlin.com, richard@nod.at, vigneshr@ti.com,
linux-mtd@lists.infradead.org, linux-kernel@vger.kernel.org,
wangle6@huawei.com, zhangweimin12@huawei.com, yebin10@huawei.com,
houtao1@huawei.com
Subject: Re: [PATCH v4] mtd: clear cache_state to avoid writing to bad blocks repeatedly
Date: Tue, 31 Mar 2020 12:05:26 +0200 [thread overview]
Message-ID: <20200331100526.GC1204199@kroah.com> (raw)
In-Reply-To: <1585618319-119741-1-git-send-email-nixiaoming@huawei.com>
On Tue, Mar 31, 2020 at 09:31:59AM +0800, Xiaoming Ni wrote:
> The function call process is as follows:
> mtd_blktrans_work()
> while (1)
> do_blktrans_request()
> mtdblock_writesect()
> do_cached_write()
> write_cached_data() /*if cache_state is STATE_DIRTY*/
> erase_write()
>
> write_cached_data() returns failure without modifying cache_state
> and cache_offset. So when do_cached_write() is called again,
> write_cached_data() will be called again to perform erase_write()
> on the same cache_offset.
>
> But if this cache_offset points to a bad block, erase_write() will
> always return -EIO. Writing to this mtdblk is equivalent to losing
> the current data, and repeatedly writing to the bad block.
>
> Repeatedly writing a bad block has no real benefits,
> but brings some negative effects:
> 1 Lost subsequent data
> 2 Loss of flash device life
> 3 erase_write() bad blocks are very time-consuming. For example:
> the function do_erase_oneblock() in chips/cfi_cmdset_0020.c or
> chips/cfi_cmdset_0002.c may take more than 20 seconds to return
>
> Therefore, when erase_write() returns -EIO in write_cached_data(),
> clear cache_state to avoid writing to bad blocks repeatedly.
>
> Signed-off-by: Xiaoming Ni <nixiaoming@huawei.com>
> Reviewed-by: Miquel Raynal <miquel.raynal@bootlin.com>
> ---
> drivers/mtd/mtdblock.c | 11 +++++++----
> 1 file changed, 7 insertions(+), 4 deletions(-)
$ ./scripts/get_maintainer.pl --file drivers/mtd/mtdblock.c
Miquel Raynal <miquel.raynal@bootlin.com> (maintainer:MEMORY TECHNOLOGY DEVICES (MTD))
Richard Weinberger <richard@nod.at> (maintainer:MEMORY TECHNOLOGY DEVICES (MTD))
Vignesh Raghavendra <vigneshr@ti.com> (maintainer:MEMORY TECHNOLOGY DEVICES (MTD))
linux-mtd@lists.infradead.org (open list:MEMORY TECHNOLOGY DEVICES (MTD))
linux-kernel@vger.kernel.org (open list)
No where on there is my name/email, so why am I getting these?
confused,
greg k-h
next prev parent reply other threads:[~2020-03-31 10:42 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-31 1:31 [PATCH v4] mtd: clear cache_state to avoid writing to bad blocks repeatedly Xiaoming Ni
2020-03-31 1:31 ` Xiaoming Ni
2020-03-31 10:05 ` Greg KH [this message]
2020-03-31 10:05 ` Greg KH
2020-03-31 11:06 ` Xiaoming Ni
2020-03-31 11:06 ` Xiaoming Ni
2020-05-07 7:53 ` ping; " Xiaoming Ni
2020-05-07 7:53 ` Xiaoming Ni
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=20200331100526.GC1204199@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=houtao1@huawei.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=miquel.raynal@bootlin.com \
--cc=nixiaoming@huawei.com \
--cc=richard@nod.at \
--cc=vigneshr@ti.com \
--cc=wangle6@huawei.com \
--cc=yebin10@huawei.com \
--cc=zhangweimin12@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.