From: Joakim Tjernlund <Joakim.Tjernlund@infinera.com>
To: "andrea.adami@gmail.com" <andrea.adami@gmail.com>
Cc: "linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>
Subject: Re: [PATCH 0/3] mtd: fix AMD/Intel flash bugs
Date: Mon, 12 Mar 2018 11:11:04 +0000 [thread overview]
Message-ID: <1520853062.4790.103.camel@infinera.com> (raw)
In-Reply-To: <CAAQYJAs93d87kWej7D6qMEcwv-3Xqb-WiZwM9M1s430vs+mzEg@mail.gmail.com>
On Mon, 2018-03-12 at 10:09 +0100, Andrea Adami wrote:
> CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe.
>
>
> On Sun, Mar 11, 2018 at 5:06 PM, Joakim Tjernlund
> <Joakim.Tjernlund@infinera.com> wrote:
> > On Thu, 2018-03-01 at 14:39 +0100, Joakim Tjernlund wrote:
> > > This fixes a bug which allows read/write to a erase block currently
> > > erasing.
> > > Also works around a chip bug in Micron 28F00AP30 chips.
> > >
> > > Joakim Tjernlund (3):
> > > cfi_cmdset_0001: Do not allow read/write to suspend erase block.
> > > cfi_cmdset_0001: Workaround Micron Erase suspend bug.
> > > cfi_cmdset_0002: Do not allow read/write to suspend erase block.
> > >
> > > drivers/mtd/chips/cfi_cmdset_0001.c | 33 ++++++++++++++++++++++++++++-----
> > > drivers/mtd/chips/cfi_cmdset_0002.c | 9 ++++++---
> > > include/linux/mtd/flashchip.h | 1 +
> > > 3 files changed, 35 insertions(+), 8 deletions(-)
> > >
> >
> > Ping?
> > This is a fairly serious bug as it confuses the flash state machine,
> > making further flash access fail.
> >
>
> Hello,
>
> I don't undertsand exactly from the titles what is happening.
> Do you want to disable erase and wite suspend like in this other 2016
> patch found around?
Not quite, the first part is about preventing read/write to a block that is
being erased. This can happen if two apps opens the same /dev/mtd device.
Then there is a bug fix for erase suspend not working in the smaller boot block
sections, that part is similar to the patch you reference but much less invasive
> https://patchwork.kernel.org/patch/9380029/
>
> See, I am user of the Sharp LH28F640BF NOR, very similar to the Intel
> Startaflash, 4-Plane Page Mode Dual Work.
> On these chips erase suspend works just fine.
> What has been disabled is dual work: simultaneous read-while-erase and
> read-while-program because there has never been real support for
> n-planes in kernel.
>
> What is exactly the issue?
> Regards
> Andrea
>
> > Jocke
> > ______________________________________________________
> > Linux MTD discussion mailing list
> > http://lists.infradead.org/mailman/listinfo/linux-mtd/
next prev parent reply other threads:[~2018-03-12 11:11 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-01 13:39 [PATCH 0/3] mtd: fix AMD/Intel flash bugs Joakim Tjernlund
2018-03-01 13:39 ` [PATCH 1/3] cfi_cmdset_0001: Do not allow read/write to suspend erase block Joakim Tjernlund
2018-03-22 14:14 ` Richard Weinberger
2018-03-22 14:26 ` Joakim Tjernlund
2018-04-24 15:45 ` Boris Brezillon
2018-03-01 13:39 ` [PATCH 2/3] cfi_cmdset_0001: Workaround Micron Erase suspend bug Joakim Tjernlund
2018-03-20 23:06 ` Richard Weinberger
2018-03-21 0:02 ` Joakim Tjernlund
2018-03-01 13:39 ` [PATCH 3/3] cfi_cmdset_0002: Do not allow read/write to suspend erase block Joakim Tjernlund
2018-03-22 14:21 ` Richard Weinberger
2018-03-22 14:27 ` Joakim Tjernlund
2018-03-11 16:06 ` [PATCH 0/3] mtd: fix AMD/Intel flash bugs Joakim Tjernlund
2018-03-12 9:09 ` Andrea Adami
2018-03-12 11:11 ` Joakim Tjernlund [this message]
2018-03-15 15:54 ` Boris Brezillon
2018-03-15 17:55 ` Joakim Tjernlund
2018-03-15 18:02 ` Boris Brezillon
2018-04-04 20:27 ` Joakim Tjernlund
2018-04-20 19:05 ` Boris Brezillon
2018-04-21 12:47 ` Joakim Tjernlund
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=1520853062.4790.103.camel@infinera.com \
--to=joakim.tjernlund@infinera.com \
--cc=andrea.adami@gmail.com \
--cc=linux-mtd@lists.infradead.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