diff options
author | Artem Bityutskiy <Artem.Bityutskiy@nokia.com> | 2011-04-21 14:49:55 +0300 |
---|---|---|
committer | Artem Bityutskiy <Artem.Bityutskiy@nokia.com> | 2011-04-21 15:27:21 +0300 |
commit | 6e0d9fd38b750d678bf9fd07db23582f52fafa55 (patch) | |
tree | e802c35a4543f1f55f782838cb946c81c124843a /crypto/compress.c | |
parent | 1a067a22e466d2910d10d47a7125bf7ced943165 (diff) | |
download | op-kernel-dev-6e0d9fd38b750d678bf9fd07db23582f52fafa55.zip op-kernel-dev-6e0d9fd38b750d678bf9fd07db23582f52fafa55.tar.gz |
UBIFS: fix master node recovery
This patch fixes the following symptoms:
1. Unmount UBIFS cleanly.
2. Start mounting UBIFS R/W and have a power cut immediately
3. Start mounting UBIFS R/O, this succeeds
4. Try to re-mount UBIFS R/W - this fails immediately or later on,
because UBIFS will write the master node to the flash area
which has been written before.
The analysis of the problem:
1. UBIFS is unmounted cleanly, both copies of the master node are clean.
2. UBIFS is being mounter R/W, starts changing master node copy 1, and
a power cut happens. The copy N1 becomes corrupted.
3. UBIFS is being mounted R/O. It notices the copy N1 is corrupted and
reads copy N2. Copy N2 is clean.
4. Because of R/O mode, UBIFS cannot recover copy 1.
5. The mount code (ubifs_mount()) sees that the master node is clean,
so it decides that no recovery is needed.
6. We are re-mounting R/W. UBIFS believes no recovery is needed and
starts updating the master node, but copy N1 is still corrupted
and was not recovered!
Fix this problem by marking the master node as dirty every time we
recover it and we are in R/O mode. This forces further recovery and
the UBIFS cleans-up the corruptions and recovers the copy N1 when
re-mounting R/W later.
Signed-off-by: Artem Bityutskiy <Artem.Bityutskiy@nokia.com>
Cc: stable@kernel.org
Diffstat (limited to 'crypto/compress.c')
0 files changed, 0 insertions, 0 deletions