On Tue, Mar 31, 2015 at 3:24 PM, Benjamin Hodgetts <b...@xnode.org> wrote:
> G. Richard Bellamy <rbellamy <at> pteradigm.com> writes:
>
>>
>> When I upgrade to the 3.19.2 Kernel I get a deadlocked boot:
>> INFO: task mount:302 blocked for more than 120 seconds.
>> INFO: task btrfs-transacti:329 blocked for more than 120 seconds.
>>
>> I have an LTS Kernel at 3.14.35 that also fails to boot with the same
> behavior.
>>
>> My 3.18.6 works just fine.
Well there are only two backports in 3.14.35. Most of the ones found
in 3.19.2 are in 3.14.36.
commit f9e2ba638c32dff17ee6404e2c8245fd49d99b8b
Author: David Sterba <dste...@suse.cz>
Date: Fri Jan 2 18:45:16 2015 +0100
btrfs: fix leak of path in btrfs_find_item
commit 381cf6587f8a8a8e981bc0c1aaaa8859b51dc756 upstream.
If btrfs_find_item is called with NULL path it allocates one locally but
does not free it. Affected paths are inserting an orphan item for a file
and for a subvol root.
Move the path allocation to the callers.
Fixes: 3f870c289900 ("btrfs: expand btrfs_find_item() to include
find_orphan_item functionality")
Signed-off-by: David Sterba <dste...@suse.cz>
Signed-off-by: Greg Kroah-Hartman <gre...@linuxfoundation.org>
commit 74e42361fa3bc102647ad1e1ec7c21b747658843
Author: David Sterba <dste...@suse.cz>
Date: Fri Dec 19 18:38:47 2014 +0100
btrfs: set proper message level for skinny metadata
commit 5efa0490cc94aee06cd8d282683e22a8ce0a0026 upstream.
This has been confusing people for too long, the message is really just
informative.
--
Chris Murphy
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
