summaryrefslogtreecommitdiffstats
path: root/fs/ubifs/Makefile
diff options
context:
space:
mode:
authorArtem Bityutskiy <Artem.Bityutskiy@nokia.com>2009-06-29 19:27:14 +0300
committerArtem Bityutskiy <Artem.Bityutskiy@nokia.com>2009-07-09 09:19:39 +0300
commit061125476039a9a998878468a6abe235b1cee347 (patch)
tree5acf6d6bc38cfd96c3d0ba4dc101d7e6a2606d16 /fs/ubifs/Makefile
parent431102fed3effe4e4e19678830ddab7f05c34bf9 (diff)
downloadop-kernel-dev-061125476039a9a998878468a6abe235b1cee347.zip
op-kernel-dev-061125476039a9a998878468a6abe235b1cee347.tar.gz
UBIFS: fix corruption dump
In the 'ubifs_recover_leb()' function, when we find corrupted empty space, we dump 8K starting from the offset where the last node ends. This is OK if the corrupted empty space is somewhere near that offset. But if the corruption is far at the end of the LEB, we will dump all 0xFF bytes and complitely ignore the interesting data. This is observed on a PPC ("kilauea") with NOR flash. This patch changes the behavior and teaches UBIFS to print only interesting data. I.e., now we find where corruption starts and start dumping from that offset. Signed-off-by: Artem Bityutskiy <Artem.Bityutskiy@nokia.com> Reviewed-by: Adrian Hunter <Adrian.Hunter@nokia.com>
Diffstat (limited to 'fs/ubifs/Makefile')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud