From: Karol Lewandowski <k.lewandowsk@samsung.com>
Date: Wed, 27 Apr 2022 15:54:45 +0000 (+0200)
Subject: block: Ensure srcpath backing loop image mount point is not null
X-Git-Tag: accepted/tizen/unified/20220428.162639^0
X-Git-Url: http://review.tizen.org/git/?a=commitdiff_plain;h=ce0dfa31d883a26d060b60fcba36c972b5bbf739;p=platform%2Fcore%2Fsystem%2Fstoraged.git

block: Ensure srcpath backing loop image mount point is not null

This commit addresses SVACE-reported issue.

Change-Id: I03871ae2cda6c5aede9582dc4be62aeb31696b4b
---

diff --git a/src/block/block.c b/src/block/block.c
index 5e51bab..bdf6e78 100644
--- a/src/block/block.c
+++ b/src/block/block.c
@@ -2574,9 +2574,13 @@ static int get_internal_storage_number(void)
 				fs = mnt_table_find_target(t, p, MNT_ITER_BACKWARD);
 				if (!fs)
 					continue;
-				const char *origtemp = temp;
-				temp = mnt_fs_get_srcpath(fs);
-				_I("%s is found under mountpoint %s on device %s (internal storage candidate)\n", origtemp, p, temp);
+
+				const char *loopmnt_srcpath = mnt_fs_get_srcpath(fs);
+				if (!loopmnt_srcpath)
+					continue;
+
+				_I("%s is found under mountpoint %s on device %s (internal storage candidate)\n", temp, p, loopmnt_srcpath);
+				temp = loopmnt_srcpath;
 				break;
 			}
 			free(backingfile_path);