From: Brian Norris <computersforpeace@gmail.com>
To: Helmut Schaa <helmut.schaa@googlemail.com>
Cc: linux-mtd@lists.infradead.org,
David Woodhouse <David.Woodhouse@intel.com>,
Artem Bityutskiy <artem.bityutskiy@linux.intel.com>,
Pekon Gupta <pekon.gupta@gmail.com>
Subject: Re: [PATCH] mtd: nand: Disable subpage writes for drivers without ecc->hwctl
Date: Wed, 9 Dec 2015 15:58:23 -0800 [thread overview]
Message-ID: <20151209235823.GD144338@google.com> (raw)
In-Reply-To: <1397034804-27161-1-git-send-email-helmut.schaa@googlemail.com>
Hi,
I have my archaeology hat on, in the deep corners of my mailbox...
On Wed, Apr 09, 2014 at 11:13:24AM +0200, Helmut Schaa wrote:
> nand_write_subpage_hwecc causes a crash if the driver did not register
> ecc->hwctl or ecc->calculate. Fix this by disabling subpage writes if
> ecc->hwctl or ecc->calculate is not provided by the driver.
>
> This behavior was introduced in commit 837a6ba4f3b6d23026674e6af6b6849a4634fff9
> "mtd: nand: subpage write support for hardware based ECC schemes".
>
> This fixes a crash with fsl_elbc_nand and maybe others:
>
[...]
>
> Cc: Gupta, Pekon <pekon@ti.com>
> Cc: Artem Bityutskiy <artem.bityutskiy@linux.intel.com>
> Cc: David Woodhouse <David.Woodhouse@intel.com>
> Signed-off-by: Helmut Schaa <helmut.schaa@googlemail.com>
> ---
> I noticed this bug on openwrt with kernel 3.10 but it looks as if this can
> still happen in more recent kernels.
>
> drivers/mtd/nand/nand_base.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/mtd/nand/nand_base.c b/drivers/mtd/nand/nand_base.c
> index 9715a7b..2298289 100644
> --- a/drivers/mtd/nand/nand_base.c
> +++ b/drivers/mtd/nand/nand_base.c
> @@ -3768,7 +3768,7 @@ int nand_scan_tail(struct mtd_info *mtd)
> ecc->write_oob = nand_write_oob_std;
> if (!ecc->read_subpage)
> ecc->read_subpage = nand_read_subpage;
> - if (!ecc->write_subpage)
> + if (!ecc->write_subpage && ecc->hwctl && ecc->calculate)
> ecc->write_subpage = nand_write_subpage_hwecc;
>
> case NAND_ECC_HW_SYNDROME:
I realize we've merged a fix for fsl_elbc_nand long ago (commit
f034d87def51 "mtd: eLBC NAND: fix subpage write support"), but this
change still looks sane, applies, and could possibly fix some other
drivers that are lurking somewhere. Any reason I shouldn't apply it?
Regards,
Brian
next prev parent reply other threads:[~2015-12-09 23:58 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-09 9:13 [PATCH] mtd: nand: Disable subpage writes for drivers without ecc->hwctl Helmut Schaa
2014-04-09 9:38 ` Gupta, Pekon
2014-04-09 10:06 ` Helmut Schaa
2014-04-09 10:33 ` Gupta, Pekon
2014-04-09 11:57 ` Helmut Schaa
2014-04-09 23:34 ` Scott Wood
2014-04-10 4:19 ` Gupta, Pekon
2014-04-10 20:47 ` Scott Wood
2014-04-10 6:45 ` Helmut Schaa
2014-04-10 7:26 ` Gupta, Pekon
2014-04-10 15:22 ` Helmut Schaa
2014-04-11 6:35 ` Gupta, Pekon
2014-04-11 20:10 ` Scott Wood
2014-04-14 5:55 ` Gupta, Pekon
2014-04-14 6:18 ` Helmut Schaa
2014-05-05 8:46 ` Gupta, Pekon
2014-05-05 16:08 ` Helmut Schaa
2015-12-09 23:58 ` Brian Norris [this message]
2015-12-10 9:31 ` Helmut Schaa
2015-12-12 0:40 ` Brian Norris
2015-12-12 7:59 ` Boris Brezillon
2015-12-14 14:04 ` Helmut Schaa
2015-12-19 2:19 ` Brian Norris
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=20151209235823.GD144338@google.com \
--to=computersforpeace@gmail.com \
--cc=David.Woodhouse@intel.com \
--cc=artem.bityutskiy@linux.intel.com \
--cc=helmut.schaa@googlemail.com \
--cc=linux-mtd@lists.infradead.org \
--cc=pekon.gupta@gmail.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).