| commit | 39b28b26cf5b7d397bbc5cd1750971efad331b4b | |
| author | Christian Borntraeger <borntraeger@de.ibm.com> | |
| Wed, 22 Nov 2017 14:26:26 +0000 (22 15:26 +0100) | ||
| committer | Cornelia Huck <cohuck@redhat.com> | |
| Thu, 14 Dec 2017 16:56:54 +0000 (14 17:56 +0100) | ||
| tree | 9e1911814255ea17d3fdb6c8f162bfbb6dc9e02b | treesnapshot (tar.gz zip) |
| parent | 0ef0583d5adceb9138bdb47494dabd1549ac5b6d | commitdiff |
s390x/migration: use zero flag parameter
valgrind pointed out that we call KVM_S390_GET_IRQ_STATE with an
undefined value for flags. Kernels prior to 4.15 did not use that
field, and later kernels ignore it for compatibility reasons, but we
better play safe.
The same is true for SET_IRQ_STATE. We should make sure to not use the
flag field, either.
Signed-off-by: Christian Borntraeger <borntraeger@de.ibm.com>
Message-Id: <20171122142627.73170-2-borntraeger@de.ibm.com>
Reviewed-by: Thomas Huth <thuth@redhat.com>
Signed-off-by: Cornelia Huck <cohuck@redhat.com>
valgrind pointed out that we call KVM_S390_GET_IRQ_STATE with an
undefined value for flags. Kernels prior to 4.15 did not use that
field, and later kernels ignore it for compatibility reasons, but we
better play safe.
The same is true for SET_IRQ_STATE. We should make sure to not use the
flag field, either.
Signed-off-by: Christian Borntraeger <borntraeger@de.ibm.com>
Message-Id: <20171122142627.73170-2-borntraeger@de.ibm.com>
Reviewed-by: Thomas Huth <thuth@redhat.com>
Signed-off-by: Cornelia Huck <cohuck@redhat.com>
| target/s390x/kvm.c | diffblobblamehistory |