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]
Date:   Thu, 18 May 2017 16:02:40 +0200
From:   David Sterba <dsterba@...e.cz>
To:     "Gustavo A. R. Silva" <garsilva@...eddedor.com>
Cc:     Chris Mason <clm@...com>, Josef Bacik <jbacik@...com>,
        linux-btrfs@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [fs-btrfs] question about apparent useless function call

On Wed, May 17, 2017 at 05:37:44PM -0500, Gustavo A. R. Silva wrote:
> While looking into Coverity ID 1398149 I ran into the following piece  
> of code at fs/btrfs/zlib.c:295:
> 
> 295done:
> 296        zlib_inflateEnd(&workspace->strm);
> 297        if (data_in)
> 298                kunmap(pages_in[page_in_index]);
> 299        if (!ret)
> 300                zero_fill_bio(orig_bio);
> 301        return ret;
> 302}
> 
> The issue here is that calling function zlib_inflateEnd() at line 296  
> _seems_ to be useless once this function _seems_ to be only useful for  
> its return value, which is ignored. The same for line 388.
> 
> Can someone help me understand what is the purpose of these calls?
> Should them be removed, or the return value actually evaluated?

I don't think that removing the functions is a good idea, even if
they're trivial in the end. The error value needs to be checked but
seems that the only thing we can do at that point is to inform the user
that something bad happen inside the decompressor.  The cleanup (kunmap
or memset) has to be done anyway.

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ