UBI: fix backward compatibility
Commit 32bc482028
did not fully fix
the backward compatibility issues. We still fail to properly handle
situations when the first PEB contains non-zero image sequence
number, but one of the following PEBs contains zero image sequence
number. For example, this may happen if we mount a new image with
an old kernel, and then try to mount it in the new kernel.
This patch should fix the issue.
Signed-off-by: Artem Bityutskiy <Artem.Bityutskiy@nokia.com>
This commit is contained in:
@ -794,16 +794,15 @@ static int process_eb(struct ubi_device *ubi, struct ubi_scan_info *si,
|
||||
* number.
|
||||
*/
|
||||
image_seq = be32_to_cpu(ech->image_seq);
|
||||
if (!si->image_seq_set) {
|
||||
if (!ubi->image_seq && image_seq)
|
||||
ubi->image_seq = image_seq;
|
||||
si->image_seq_set = 1;
|
||||
} else if (ubi->image_seq && ubi->image_seq != image_seq) {
|
||||
if (ubi->image_seq && image_seq &&
|
||||
ubi->image_seq != image_seq) {
|
||||
ubi_err("bad image sequence number %d in PEB %d, "
|
||||
"expected %d", image_seq, pnum, ubi->image_seq);
|
||||
ubi_dbg_dump_ec_hdr(ech);
|
||||
return -EINVAL;
|
||||
}
|
||||
|
||||
}
|
||||
|
||||
/* OK, we've done with the EC header, let's look at the VID header */
|
||||
|
Reference in New Issue
Block a user