avoid future chance of using uninitialized memory
authorDaniel Kahn Gillmor <dkg@fifthhorseman.net>
Fri, 19 Dec 2014 22:53:36 +0000 (17:53 -0500)
committerNIIBE Yutaka <gniibe@fsij.org>
Tue, 13 Jan 2015 01:52:22 +0000 (10:52 +0900)
commit1fc4dc541af7d4bf4dba6ef37d1d7841498a05c6
tree16f2af3a6bf36680a02d081defab0ff64b43c987
parentf542826b04e35f13a30116564daaf6456440b1d4
avoid future chance of using uninitialized memory

* common/iobuf.c: (iobuf_open): initialize len

--

In iobuf_open, IOBUFCTRL_DESC and IOBUFCTRL_INIT commands are invoked
(via file_filter()) on fcx, passing in a pointer to an uninitialized
len.

With these two commands, file_filter doesn't actually do anything with
the value of len, so there's no actual risk of use of uninitialized
memory in the code as it stands.

However, some static analysis tools might flag this situation with a
warning, and initializing the value doesn't hurt anything, so i think
this trivial cleanup is warranted.

Debian-Bug-Id: 773469
common/iobuf.c