From: "Li, ZhenHua" <zhen-hual@hp.com>
To: Heinrich Schuchardt <xypron.glpk@gmx.de>
Cc: "Yann E. MORIN" <yann.morin.1998@free.fr>,
"linux-kbuild@vger.kernel.org" <linux-kbuild@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/1] script/kconfig: remove a warning for menucofig
Date: Tue, 15 Jul 2014 16:53:55 +0800 [thread overview]
Message-ID: <53C4EC23.4060309@hp.com> (raw)
In-Reply-To: <53C40589.8050202@gmx.de>
Heinrich,
Thank you very much for reviewing. But seems the maintainer will not
accept it.
Zhenhua
On 07/15/2014 12:30 AM, Heinrich Schuchardt wrote:
> On 01.07.2014 01:10, Li, Zhen-Hua wrote:
>> When malloc for jump,
>> if (head && location) {
>> jump = xmalloc(sizeof(struct jump_key));
>> ....
>> }
>> And here it is used:
>> if (head && location && menu == location)
>> jump->offset = strlen(r->s);
>>
>>
>> So I think when jump is used, it must not be NULL; then !=NULL is not
>> needed.
>
> I tested the patch against v13.6-rc5. It fixes the problem with the
> warning.
>
> You can add
>
> Reviewed-by: Heinrich Schuchardt <xypron.glpk@gmx.de>
>
> Best regards
>
> Heinrich
>
>
>> -----Original Message-----
>> From: Heinrich Schuchardt [mailto:xypron.glpk@gmx.de]
>> Sent: Tuesday, July 01, 2014 1:03 AM
>> To: Li, Zhen-Hua; Yann E. MORIN; linux-kbuild@vger.kernel.org;
>> linux-kernel@vger.kernel.org
>> Subject: Re: [PATCH 1/1] script/kconfig: remove a warning for menucofig
>>
>> On 30.06.2014 05:16, Li, Zhen-Hua wrote:
>>> There is a warning when run "make menuconfig".
>>>
>>> scripts/kconfig/menu.c: In function ‘get_symbol_str’:
>>> scripts/kconfig/menu.c:591:18: warning: ‘jump’ may be used
>>> uninitialized in
>>> this function [-Wmaybe-uninitialized]
>>> jump->offset = strlen(r->s);
>>> ^
>>> scripts/kconfig/menu.c:551:19: note: ‘jump’ was declared here
>>> struct jump_key *jump;
>>> ^
>>>
>>> It is because the compiler think "jump" is not initialized, though
>>> in fact
>>> it is already initialized.
>>>
>>> Signed-off-by: Li, Zhen-Hua <zhen-hual@hp.com>
>>> ---
>>> scripts/kconfig/menu.c | 2 +-
>>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>>
>>> diff --git a/scripts/kconfig/menu.c b/scripts/kconfig/menu.c
>>> index a26cc5d..584e0fc 100644
>>> --- a/scripts/kconfig/menu.c
>>> +++ b/scripts/kconfig/menu.c
>>> @@ -548,7 +548,7 @@ static void get_prompt_str(struct gstr *r,
>>> struct property *prop,
>>> {
>>> int i, j;
>>> struct menu *submenu[8], *menu, *location = NULL;
>>> - struct jump_key *jump;
>>> + struct jump_key *jump = NULL;
>>>
>>> str_printf(r, _("Prompt: %s\n"), _(prop->text));
>>> menu = prop->menu->parent;
>>>
>> Hello Zhen-Hua,
>>
>> the patch looks incomplete to me. A check
>> jump != NULL
>> should be added before accessing parts of structure jump_key.
>>
>> Best regards
>>
>> Heinrich Schuchardt
>>
>
next prev parent reply other threads:[~2014-07-15 8:55 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-30 3:16 [PATCH 1/1] script/kconfig: remove a warning for menucofig Li, Zhen-Hua
2014-06-30 3:16 ` Li, Zhen-Hua
2014-06-30 17:02 ` Heinrich Schuchardt
2014-06-30 23:10 ` Li, Zhen-Hua
2014-06-30 23:10 ` Li, Zhen-Hua
2014-07-14 16:30 ` Heinrich Schuchardt
2014-07-15 8:53 ` Li, ZhenHua [this message]
2014-07-14 6:25 ` Li, ZhenHua
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=53C4EC23.4060309@hp.com \
--to=zhen-hual@hp.com \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=xypron.glpk@gmx.de \
--cc=yann.morin.1998@free.fr \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.