mtd/ubi/attach.c

47  * the reason is a power cut, UBI puts this PEB to the @erase list, and all
52  * Obviously, this lessens the amount of available PEBs, and if at some  point
64  *     to just erase this PEB - this is corruption type 1.
67  *     happened, so this is corruption type 1. However, this is just a guess,
69  *   o Otherwise this is corruption type 2.
110 	/* Walk the volume RB-tree to look if this volume is already present */
319  * @av: information about the volume this logical eraseblock belongs to
343 		 * This is not the first logical eraseblock belonging to this
391  * present in the attaching information, this function does nothing. Otherwise
427  * case of success this function returns a positive value, in case of failure, a
468 	 * Note: this may be optimized so that we wouldn't read twice.
554  * @bitflips: if bit-flips were detected when this physical eraseblock was read
558  * because it has to handle cases when this is not the first physical
588 	 * if this is the first instance of this logical eraseblock or not.
609 		dbg_bld("this LEB already exists: PEB %d, sqnum %llu, EC %d",
680 	 * We've met this logical eraseblock for the first time, add it to the
730  * are no data about this volume in the attaching information.
858  * @vid_hdr: the (corrupted) VID header of this PEB
864  * because of a power cut (%0 is returned in this case). Otherwise, it was
865  * probably corrupted for some other reasons (%1 is returned in this case). A
868  * If the corruption reason was a power cut, UBI can safely erase this PEB.
886 		 * this, but presumably a power cut happened while this PEB was
902 	ubi_err(ubi, "this may be a non-UBI PEB or a severe VID header corruption which requires manual inspection");
937  * information about this PEB to the corresponding list or RB-tree in the
982 		 * corrupted. Set %bitflips flag in order to make this PEB be
1000 			ubi_err(ubi, "this UBI version is %d, image version is %d",
1010 			 * values, as this seems to be enough for any existing
1027 		 * For this reasons, we do not panic if some PEBs have zero
1057 			 * with data integrity error, probably this is a bad
1081 			 * that this a valid UBI PEB which has corresponding
1085 			 * operation. So we just schedule this PEB for erasure.
1204  * corrupted PEBs and we should not attach this MTD device. Returns zero if we
1248 		 *    want to go ahead and format this flash. While formatting,
1281 	struct rb_node *this = av->root.rb_node;
1283 	while (this) {
1284 		if (this->rb_left)
1285 			this = this->rb_left;
1286 		else if (this->rb_right)
1287 			this = this->rb_right;
1289 			aeb = rb_entry(this, struct ubi_ainf_peb, u.rb);
1290 			this = rb_parent(this);
1291 			if (this) {
1292 				if (this->rb_left == &aeb->u.rb)
1293 					this->rb_left = NULL;
1295 					this->rb_right = NULL;
1368  * @start: start scanning at this PEB