summaryrefslogtreecommitdiff
path: root/drivers/mtd
diff options
context:
space:
mode:
authorPeter Horton <zero@colonel-panic.org>2010-01-05 11:14:36 +0000
committerArtem Bityutskiy <Artem.Bityutskiy@nokia.com>2010-01-12 13:19:08 +0200
commitff998793288b49a3b22d929bf8e56362320905ff (patch)
tree2f11b74d60bebec123fb26c7cb22af5c5eb0af81 /drivers/mtd
parent74d2e4f8d79ae0c4b6ec027958d5b18058662eea (diff)
downloadlinux-3.10-ff998793288b49a3b22d929bf8e56362320905ff.tar.gz
linux-3.10-ff998793288b49a3b22d929bf8e56362320905ff.tar.bz2
linux-3.10-ff998793288b49a3b22d929bf8e56362320905ff.zip
UBI: initialise update marker
The in kernel copy of a volume's update marker is not initialised from the volume table. This means that volumes where an update was unfinnished will not be treated as "forbidden to use". This is basically that the update functionality was broken. Signed-off-by: Peter Horton <zero@colonel-panic.org> Signed-off-by: Artem Bityutskiy <Artem.Bityutskiy@nokia.com> Cc: stable@kernel.org
Diffstat (limited to 'drivers/mtd')
-rw-r--r--drivers/mtd/ubi/vtbl.c1
1 files changed, 1 insertions, 0 deletions
diff --git a/drivers/mtd/ubi/vtbl.c b/drivers/mtd/ubi/vtbl.c
index 1afc61e7455..40044028d68 100644
--- a/drivers/mtd/ubi/vtbl.c
+++ b/drivers/mtd/ubi/vtbl.c
@@ -566,6 +566,7 @@ static int init_volumes(struct ubi_device *ubi, const struct ubi_scan_info *si,
vol->reserved_pebs = be32_to_cpu(vtbl[i].reserved_pebs);
vol->alignment = be32_to_cpu(vtbl[i].alignment);
vol->data_pad = be32_to_cpu(vtbl[i].data_pad);
+ vol->upd_marker = vtbl[i].upd_marker;
vol->vol_type = vtbl[i].vol_type == UBI_VID_DYNAMIC ?
UBI_DYNAMIC_VOLUME : UBI_STATIC_VOLUME;
vol->name_len = be16_to_cpu(vtbl[i].name_len);