summaryrefslogtreecommitdiffstats
path: root/fs/ubifs/shrinker.c
diff options
context:
space:
mode:
authorArtem Bityutskiy <Artem.Bityutskiy@nokia.com>2011-05-26 08:58:19 +0300
committerArtem Bityutskiy <Artem.Bityutskiy@nokia.com>2011-06-01 12:29:06 +0300
commitda8b94ea61c5d80aae0cc7b7541f1e0fa7459391 (patch)
tree5d0b7c64b7f5afd9c9b2c528ed08e7d8a0d97859 /fs/ubifs/shrinker.c
parentefcfde54ca68091b164f9aec544c7233a9760aff (diff)
downloadop-kernel-dev-da8b94ea61c5d80aae0cc7b7541f1e0fa7459391.zip
op-kernel-dev-da8b94ea61c5d80aae0cc7b7541f1e0fa7459391.tar.gz
UBIFS: fix recovery broken by the previous recovery fix
Unfortunately, the recovery fix d1606a59b6be4ea392eabd40d1250aa1eeb19efb (UBIFS: fix extremely rare mount failure) broke recovery. This commit make UBIFS drop the last min. I/O unit in all journal heads, but this is needed only for the GC head. And this does not work for non-GC heads. For example, if suppose we have min. I/O units A and B, and A contains a valid node X, which was fsynced, and then a group of nodes Y which spans the rest of A and B. In this case we'll drop not only Y, but also X, which is obviously incorrect. This patch fixes the issue and additionally makes recovery to drop last min. I/O unit only for the GC head, and leave things as they have been for ages for the other heads - this is safer. Signed-off-by: Artem Bityutskiy <Artem.Bityutskiy@nokia.com>
Diffstat (limited to 'fs/ubifs/shrinker.c')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud