diff options
| author | Brian Behlendorf <[email protected]> | 2015-11-09 12:10:02 -0800 |
|---|---|---|
| committer | Brian Behlendorf <[email protected]> | 2016-01-29 14:11:11 -0800 |
| commit | 84638a5d0c69eb8725dbf94ee7c7bece7a597bc2 (patch) | |
| tree | db65fc5113152677dfeca32a0df797790ac59a49 /rpm/generic/zfs-kmod.spec.in | |
| parent | 9986e9f5446fb675a6eabb16400503d5a23fd5a9 (diff) | |
Fix maybe uninitialized
As of gcc 5.1.1 20150618 (Red Hat 5.1.1-4) the -Werror=maybe-uninitialized
check detects that 'snapname' in recv_incremental_replication() may not be
initialized. Explicitly initialize the variable to resolved the warning.
libzfs_sendrecv.c: In function ‘recv_incremental_replication’:
libzfs_sendrecv.c:2019:2: error: ‘snapname’ may be used uninitialized in
(void) snprintf(buf, sizeof (buf), "%s@%s", fsname, snapname);
Signed-off-by: Brian Behlendorf <[email protected]>
Diffstat (limited to 'rpm/generic/zfs-kmod.spec.in')
0 files changed, 0 insertions, 0 deletions