From mboxrd@z Thu Jan  1 00:00:00 1970
From: Qu Wenruo <wqu@suse.com>
Date: Mon, 2 Nov 2020 15:27:59 +0800
Subject: [PATCH 4/4] fs: btrfs: initialize @ii in show_dir() to make
 coverity happy
In-Reply-To: <20201102082409.7b5cce51@nic.cz>
References: <20201031010752.23974-1-wqu@suse.com>
 <20201031010752.23974-5-wqu@suse.com> <20201102000656.241101c5@nic.cz>
 <2e5530d6-e5e9-8c4b-686c-5c39b8339c86@suse.com>
 <20201102082409.7b5cce51@nic.cz>
Message-ID: <70132001-1e9c-8e5f-5ced-5b2ae6c198da@suse.com>
List-Id: <u-boot.lists.denx.de>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
To: u-boot@lists.denx.de



On 2020/11/2 ??3:24, Marek Behun wrote:
> On Mon, 2 Nov 2020 08:27:16 +0800
> Qu Wenruo <wqu@suse.com> wrote:
> 
>> Thus I really tend to believe it's just a bug in coverity.
>> All locations accessing @ii all have its key.type checked to ensure it get filled in the first place.
> 
> If this is a bug in coverity, we should fix coverity, not add extra
> code to U-Boot, even if it is just one instruction. That simply stinks
> the same way like when systemd crashed when "debug" parameter was
> present in /proc/cmdline, and they sent a patch to kernel which removed
> the "debug" parameter, instead of fixing systemd. IMO.

Yep, you're right.

Please discard this patch.

Thanks,
Qu

> 
> Marek
>