linux-kernel - Re: [PATCH] tools/libbpf: Avoid possibly using uninitialized variable

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <e654d851-7dd1-d395-c83a-b5d0cc8b211f@iogearbox.net>
Date:   Tue, 20 Feb 2018 21:32:14 +0100
From:   Daniel Borkmann <daniel@...earbox.net>
To:     Jeremy Cline <jeremy@...ine.org>,
        Alexei Starovoitov <ast@...nel.org>
Cc:     netdev@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] tools/libbpf: Avoid possibly using uninitialized variable

On 02/20/2018 02:00 AM, Jeremy Cline wrote:
> Fixes a GCC maybe-uninitialized warning introduced by 48cca7e44f9f.
> "text" is only initialized inside the if statement so only print debug
> info there.
> 
> Signed-off-by: Jeremy Cline <jeremy@...ine.org>

Looks good, applied to bpf tree, thanks Jeremy!