Patch "UBI: initialize LEB number variable" has been added to the 3.14-stable tree

This is a note to let you know that I've just added the patch titled

UBI: initialize LEB number variable

to the 3.14-stable tree which can be found at:
http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary

The filename of the patch is:
ubi-initialize-leb-number-variable.patch
and it can be found in the queue-3.14 subdirectory.

If you, or anyone else, feels it should not be added to the stable tree, please let <[email protected]> know about it.

From: Brian Norris <[email protected]>
Date: Sat, 28 Feb 2015 02:23:27 -0800
Subject: UBI: initialize LEB number variable

From: Brian Norris <[email protected]>

commit f16db8071ce18819fbd705ddcc91c6f392fb61f8 upstream.

In some of the 'out_not_moved' error paths, lnum may be used uninitialized. Don't ignore the warning; let's fix it.

This uninitialized variable doesn't have much visible effect in the end, since we just schedule the PEB for erasure, and its LEB number doesn't really matter (it just gets printed in debug messages). But let's get it straight anyway.

Coverity CID #113449

---
 drivers/mtd/ubi/wl.c |    2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

@@ -995,7 +995,7 @@ static int wear_leveling_worker(struct u
 				int cancel)
 {
 	int err, scrubbing = 0, torture = 0, protect = 0, erroneous = 0;
-	int vol_id = -1, uninitialized_var(lnum);
+	int vol_id = -1, lnum = -1;
 #ifdef CONFIG_MTD_UBI_FASTMAP
 	int anchor = wrk->anchor;
 #endif

Patches currently in stable-queue which might be from [email protected] are

queue-3.14/ubi-initialize-leb-number-variable.patch queue-3.14/ubi-fix-out-of-bounds-write.patch queue-3.14/ubi-account-for-bitflips-in-both-the-vid-header-and-data.patch queue-3.14/ubi-fix-check-for-too-many-bytes.patch