Patch "Btrfs: fix uninit variable in clone ioctl" has been added to the 4.0-stable tree

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

Btrfs: fix uninit variable in clone ioctl

to the 4.0-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:
btrfs-fix-uninit-variable-in-clone-ioctl.patch
and it can be found in the queue-4.0 subdirectory.

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

From: Chris Mason <[email protected]>
Date: Sat, 11 Apr 2015 05:09:06 -0700
Subject: Btrfs: fix uninit variable in clone ioctl

From: Chris Mason <[email protected]>

commit de249e66a73d696666281cd812087979c6fae552 upstream.

Commit 0d97a64e0 creates a new variable but doesn't always set it up. This puts it back to the original method (key.offset + 1) for the cases not covered by Filipe's new logic.

---
 fs/btrfs/ioctl.c |    2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

@@ -3206,7 +3206,7 @@ static int btrfs_clone(struct inode *src
 	key.offset = off;
 
 	while (1) {
-		u64 next_key_min_offset;
+		u64 next_key_min_offset = key.offset + 1;
 
 		/*
 		 * note the key will change type as we walk through the

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

queue-4.0/btrfs-fix-regression-in-raid-level-conversion.patch queue-4.0/btrfs-send-add-missing-check-for-dead-clone-root.patch queue-4.0/btrfs-incorrect-handling-for-fiemap_fill_next_extent-return.patch queue-4.0/btrfs-send-don-t-leave-without-decrementing-clone-root-s-send_progress.patch queue-4.0/btrfs-fix-range-cloning-when-same-inode-used-as-source-and-destination.patch queue-4.0/btrfs-fix-uninit-variable-in-clone-ioctl.patch queue-4.0/btrfs-cleanup-orphans-while-looking-up-default-subvolume.patch --
To unsubscribe from this list: send the line "unsubscribe stable" in