File 0170-btrfs-progs-check-release-path-after-usage... of Package btrfsprogs

Overview Repositories Revisions Requests Users Attributes Meta

File 0170-btrfs-progs-check-release-path-after-usage.patch of Package btrfsprogs (Revision 09e6a55540f62d57afdac5eb5a0f7d7d)

Currently displaying revision 09e6a55540f62d57afdac5eb5a0f7d7d , Show latest

From: Goldwyn Rodrigues <rgoldwyn@suse.com>
Date: Mon, 24 Oct 2016 10:18:14 -0500
Subject: btrfs-progs: check: release path after usage
Git-commit: a7ec18a8640338fd9b4fd2424012f78f31fcef38
Patch-mainline: v4.8.2
References: bsc#997061

While performing an fsck, an assertion failure occurs because of reusing path in a loop.
ctree.c:1112: btrfs_search_slot: Warning: assertion `p->nodes[0] != NULL` failed, value 0

Signed-off-by: Goldwyn Rodrigues <rgoldwyn@suse.com>
Signed-off-by: David Sterba <dsterba@suse.com>
Acked-by: Jeff Mahoney <jeffm@suse.com>
---
 cmds-check.c | 1 +
 1 file changed, 1 insertion(+)

diff --git a/cmds-check.c b/cmds-check.c
index 907d60c..7718c7b 100644
--- a/cmds-check.c
+++ b/cmds-check.c
@@ -7544,6 +7544,7 @@ static int record_orphan_data_extents(struct btrfs_fs_info *fs_info,
 		key.offset = dback->offset;
 
 		ret = btrfs_search_slot(NULL, dest_root, &key, path, 0, 0);
+		btrfs_release_path(path);
 		/*
 		 * For ret < 0, it's OK since the fs-tree may be corrupted,
 		 * we need to record it for inode/file extent rebuild.

Places

File 0170-btrfs-progs-check-release-path-after-usage.patch of Package btrfsprogs (Revision 09e6a55540f62d57afdac5eb5a0f7d7d)

Places