From: Martin Walch <walch.martin@web.de>
Date: Thu, 3 Oct 2013 16:35:16 +0000 (+0200)
Subject: kconfig: fix bug in search results string: use strlen(gstr->s), not gstr->len
X-Git-Url: https://git.stricted.de/?a=commitdiff_plain;h=503c823048e81cc85c0e9d8c297cc70203e335e5;p=GitHub%2FLineageOS%2Fandroid_kernel_motorola_exynos9610.git

kconfig: fix bug in search results string: use strlen(gstr->s), not gstr->len

The struct gstr has a capacity that may differ from the actual string length.

However, a string manipulation in the function search_conf made the assumption
that it is the same, which led to messing up some search results, especially
when the content of the gstr in use had not yet reached at least 63 chars.

Signed-off-by: Martin Walch <walch.martin@web.de>
Acked-by: Wang YanQing <udknight@gmail.com>
Acked-by: Benjamin Poirier <bpoirier@suse.de>
Reviewed-by: "Yann E. MORIN" <yann.morin.1998@free.fr>
Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr>
---

diff --git a/scripts/kconfig/menu.c b/scripts/kconfig/menu.c
index 9e69f1934836..db1512ae30cc 100644
--- a/scripts/kconfig/menu.c
+++ b/scripts/kconfig/menu.c
@@ -584,7 +584,7 @@ static void get_prompt_str(struct gstr *r, struct property *prop,
 		for (j = 4; --i >= 0; j += 2) {
 			menu = submenu[i];
 			if (head && location && menu == location)
-				jump->offset = r->len - 1;
+				jump->offset = strlen(r->s);
 			str_printf(r, "%*c-> %s", j, ' ',
 				   _(menu_get_prompt(menu)));
 			if (menu->sym) {