public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Boris Brezillon <boris.brezillon@bootlin.com>
To: Richard Weinberger <richard@nod.at>
Cc: Olivier Schonken <olivier.schonken@gmail.com>,
	David Woodhouse <dwmw2@infradead.org>,
	Brian Norris <computersforpeace@gmail.com>,
	linux-mtd@lists.infradead.org,
	Marek Vasut <marek.vasut@gmail.com>
Subject: Re: Atmel Nand PMECC UBI ECC issue
Date: Wed, 28 Mar 2018 10:32:04 +0200	[thread overview]
Message-ID: <20180328103204.5272349a@bbrezillon> (raw)
In-Reply-To: <3546894.3QeRhpBW0o@blindfold>

On Tue, 27 Mar 2018 16:08:46 +0200
Richard Weinberger <richard@nod.at> wrote:

> Oliver,
> 
> Am Dienstag, 27. März 2018, 10:28:52 CEST schrieb Olivier Schonken:
> > Hi Richard
> > 
> > The bytes in question is at offset 36c90.  
> 
> Okay. At this offset we have a UBIFS data node of length 1477.
> One bit of the UBIFS magic changed. 0x30 instead of 0x31
> Fun fact, the UBIFS CRC32 is correct. UBIFS magic and the CRC32 are not 
> covered by the CRC.
> So, really just one bit changed, in the magic.

Looks like this problem was caused by a bug in the atmel NFC driver.
Fix is available here [1].

Regards,

Boris

[1]http://patchwork.ozlabs.org/patch/891725/
-- 
Boris Brezillon, Bootlin (formerly Free Electrons)
Embedded Linux and Kernel engineering
https://bootlin.com

      reply	other threads:[~2018-03-28  8:32 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-26 14:56 Atmel Nand PMECC UBI ECC issue Olivier Schonken
2018-03-26 20:07 ` Richard Weinberger
2018-03-27  8:28   ` Olivier Schonken
2018-03-27 14:08     ` Richard Weinberger
2018-03-28  8:32       ` Boris Brezillon [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=20180328103204.5272349a@bbrezillon \
    --to=boris.brezillon@bootlin.com \
    --cc=computersforpeace@gmail.com \
    --cc=dwmw2@infradead.org \
    --cc=linux-mtd@lists.infradead.org \
    --cc=marek.vasut@gmail.com \
    --cc=olivier.schonken@gmail.com \
    --cc=richard@nod.at \
    /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