All of lore.kernel.org
 help / color / mirror / Atom feed
From: Steven Scholz <steven.scholz@imc-berlin.de>
To: Ferenc Havasi <havasi@inf.u-szeged.hu>
Cc: linux-mtd@lists.infradead.org
Subject: Re: JFFS2: checking CRCs twice!?
Date: Wed, 12 Jan 2005 15:05:33 +0100	[thread overview]
Message-ID: <41E52EAD.2090302@imc-berlin.de> (raw)
In-Reply-To: <41E4EDBE.8070302@inf.u-szeged.hu>

Hi Ferenc,

Ferenc Havasi wrote:

> If I am right there are two kind of CRC: hdr_crc and node_crc. At 
> mounting time only the hdr_crc is checked which depends on only the 
> header. (using summary there is only one summary CRC check)
> 
> Later (when the data is readed or in the background by GC) the node_crc 
> will also be checked. GC is running on a "niced" (10) priority, so it 
> should not disturb any other process.
Well, it does. On small, slow systems.

> If I am right the CRC protects against unclean reboots and hardware 
> corruptions. If you need we can modify the summary patch not to check 
> node_crc for summarized nodes (where the unclean reboots is no problem), 
That would be nice.

> but if we do it you lose the ability to detect the hardware corruption 
> (flash errors). Unfortunatelly NOR flash doesn't have any error detection.
Well. I think when a sectors gots written correctly (and summary is correct), I 
have to assume that the sector stay intact. So no need for checks.

If a sector got broken just by reading it then the whole embedded system is 
broken and has to be replaced ...

-- 
Steven Scholz

  reply	other threads:[~2005-01-12 14:05 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-12  7:51 JFFS2: checking CRCs twice!? Steven Scholz
2005-01-12  9:28 ` Ferenc Havasi
2005-01-12 14:05   ` Steven Scholz [this message]
2005-01-12 15:11     ` Artem B. Bityuckiy
2005-01-12 15:16       ` Steven Scholz
2005-01-12 15:21         ` Artem B. Bityuckiy
2005-01-12 15:28           ` Josh Boyer
2005-01-12 15:33           ` Steven Scholz
2005-01-14 10:24           ` Steven Scholz
2005-01-14 11:07             ` Artem B. Bityuckiy
2005-01-12 18:26       ` Jörn Engel
2005-01-12 18:43         ` Josh Boyer
2005-01-12 18:50           ` Jörn Engel
2005-01-12  9:35 ` Artem B. Bityuckiy
2005-01-12 10:08   ` Artem B. Bityuckiy

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=41E52EAD.2090302@imc-berlin.de \
    --to=steven.scholz@imc-berlin.de \
    --cc=havasi@inf.u-szeged.hu \
    --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 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.