mtd/ubi/attach.c

33  * whether the headers are corrupted or not. Sometimes UBI also protects the
58  * scanning). UBI assumes corruption type 2 if the VID header is corrupted and
223  * basically means it will be processed first later. E.g., we add corrupted
224  * PEBs (corrupted due to power cuts) to the head of the erase list to make
258  * add_corrupted - add a corrupted physical eraseblock.
263  * This function allocates a 'struct ubi_ainf_peb' object for a corrupted
272 	dbg_bld("add to corrupted: PEB %d, EC %d", pnum, ec);
435  *     o bit 2 is cleared: the older LEB is not corrupted;
436  *     o bit 2 is set: the older LEB is corrupted.
441 	int len, err, second_is_newer, bitflips = 0, corrupted = 0;
522 		corrupted = 1;
538 	return second_is_newer | (bitflips << 1) | (corrupted << 2);
858  * @vid_hdr: the (corrupted) VID header of this PEB
863  * 0xFF bytes in the data area, the VID header is most probably corrupted
865  * probably corrupted for some other reasons (%1 is returned in this case). A
887 		 * erased, so it became unstable and corrupted, and should be
900 	ubi_err(ubi, "PEB %d contains corrupted VID header, and the data does not contain all 0xFF",
982 		 * corrupted. Set %bitflips flag in order to make this PEB be
1056 			 * Both EC and VID headers are corrupted and were read
1080 			 * Both headers are corrupted. There is a possibility
1082 			 * LEB, but the headers are corrupted. However, it is
1094 			 * The EC was OK, but the VID header is corrupted. We
1172 		ubi_warn(ubi, "valid VID header but corrupted EC header at PEB %d",
1204  * corrupted PEBs and we should not attach this MTD device. Returns zero if we
1216 	 * Few corrupted PEBs is not a problem and may be just a result of
1221 		ubi_err(ubi, "%d PEBs are corrupted and preserved",
1229 		 * If too many PEBs are corrupted, we refuse attaching,
1233 			ubi_err(ubi, "too many corrupted PEBs, refusing");