[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20210401151643.GW7604@twin.jikos.cz>
Date: Thu, 1 Apr 2021 17:16:43 +0200
From: David Sterba <dsterba@...e.cz>
To: Jiapeng Chong <jiapeng.chong@...ux.alibaba.com>
Cc: clm@...com, josef@...icpanda.com, dsterba@...e.com,
linux-btrfs@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] btrfs: Remove useless call "zlib_inflateEnd"
On Tue, Mar 30, 2021 at 06:17:01PM +0800, Jiapeng Chong wrote:
> Fix the following whitescan warning:
>
> Calling "zlib_inflateEnd(&workspace->strm)" is only useful for its
> return value, which is ignored.
According to the zlib API documentation in include/linux/zlib.h
301 extern int zlib_deflateEnd (z_streamp strm);
302 /*
303 All dynamically allocated data structures for this stream are freed.
304 This function discards any unprocessed input and does not flush any
305 pending output.
306
307 deflateEnd returns Z_OK if success, Z_STREAM_ERROR if the
308 stream state was inconsistent, Z_DATA_ERROR if the stream was freed
309 prematurely (some input or output was discarded). In the error case,
310 msg may be set but then points to a static string (which must not be
311 deallocated).
312 */
The first paragraph says it could free data, so the call needs to be
there. The return value could have some meaning as it could point out to
some inconsistency in zlib internal state but just deleting is IMO
wrong.
Powered by blists - more mailing lists