aboutsummaryrefslogtreecommitdiffstats
path: root/fs/ubifs/ubifs.h
diff options
context:
space:
mode:
authorArtem Bityutskiy <Artem.Bityutskiy@nokia.com>2011-02-02 09:22:54 +0200
committerArtem Bityutskiy <Artem.Bityutskiy@nokia.com>2011-03-08 10:12:49 +0200
commit2765df7da540687c4d57ca840182122f074c5b9c (patch)
treec3dcf4c3ae4c6596ca0ac61a119274b7b4e782c4 /fs/ubifs/ubifs.h
parent6c7f74f703cc4baf053270a6e78a32f832f03445 (diff)
downloadkernel_samsung_tuna-2765df7da540687c4d57ca840182122f074c5b9c.zip
kernel_samsung_tuna-2765df7da540687c4d57ca840182122f074c5b9c.tar.gz
kernel_samsung_tuna-2765df7da540687c4d57ca840182122f074c5b9c.tar.bz2
UBIFS: use max_write_size during recovery
When recovering from unclean reboots UBIFS scans the journal and checks nodes. If a corrupted node is found, UBIFS tries to check if this is the last node in the LEB or not. This is is done by checking if there only 0xFF bytes starting from the next min. I/O unit. However, since now we write in c->max_write_size, we should actually check for 0xFFs starting from the next max. write unit. Signed-off-by: Artem Bityutskiy <Artem.Bityutskiy@nokia.com>
Diffstat (limited to 'fs/ubifs/ubifs.h')
0 files changed, 0 insertions, 0 deletions